I see the roles/persmissions are defined at the archestra dashboard level, over what an user is able and not able to do. Is there a way, I can get it more workflow levels, for example, APIs for disabling access for a user to A2A Gateway or MCP Gateway or LLM Gateway?
Hi team! :rotating_light:
Quick question about MCP Gateway tool policies:
I've set `agent-mesh-tools__docker_status` to **"Blocked"** in the Tool Policies page, but when I call it through the MCP Gateway, it still executes successfully.
**Setup:**
• Gateway: `dac6e444-f791-423b-b724-4df4edae8182`
• Profile: Default Profile
• Using Authorization Bearer token
• Endpoint: `localhost:9000/v1/mcp/{gateway-id}`
**Expected:** Policy violation error
**Actual:** Tool runs normally
Is there an additional step needed to enforce policies? Or should policies only apply to LLM Proxy calls, not direct MCP client calls?
Screenshots attached showing the blocked status in UI.
Thanks!
when using archestra, (e.g. in the archestra-openclaw example docker setup), do you always get the dual-llm-injection-prevention out of the box for every single request?
Hello everyone! Im finding my way around Archestra, its the first time Im using a tool like this. I wanted to install a Google Workspace MCP server, but I'm facing some issues. Is it supported?
I see MCP servers have recommended protocol of OAuth2.1. But if I were to try adding it to Archestra set up using _Add MCP Server to the Private Registry,_ and select OAuth2.0; will the auth work as usual?
when you run the archestra/platform docker container, it seems to auto-start another container, kindest/node:v1.35.0, for the mcp control plane. this is an "interesting" pattern. i prefer having all my containers defined in docker-compose
New release! 🚀🚀🚀
*1.0.42 (2026-02-10)*
Features
* add custom vault injector (#2698) (09fa98e)
* add MCP metrics/tracing (#2699) (8ecdccf)
Bug Fixes
* cleanup stale sessions and fix catalog config comparison (#2701) (952f431)
* detect "session not found" and retry with fresh session (#2703) (7d9eee6)
* detect stale session with ping (#2705) (7379620)
* revert organization logo preview when upload fails (#2680) (34e61d6)
Miscellaneous Chores
* deduplicate metrics `sanitizeLabelKey` util function (#2709) (85d82ca)
* remove "Show Tool calls" toggle button from chat header (#2710) (ea9dfe0), closes #2643
* rename "credential type" to "installation type" and replace radio buttons with dropdown (#2711) (950b27e)
Pathan Aymaan —
Hi team — quick question about A2A agents.
I’m calling an agent via A2A (`/v1/a2a/{agentId}`) and the request reaches the agent, but execution fails with:
> *“LLM Provider API key not configured. Please configure it in Chat Settings.”*
I already added an API key in Chat Settings and MCP tools are working fine.
Do A2A agents require a separate provider/model binding in the Agent config itself?
Thanks 👍
Oswald Shilo —
Hello @everyone, this is Oswald. I’m currently an undergraduate student, but I already have some experience working with a Simple MCP Server.
I would really appreciate some guidance on how to get started here, because many of the terms being used feel quite technical to me.
> 👋 Hi everyone, I’m Tushar. Looking forward to hacking together and learning from you all. Great to meet the community!
Tushar Khatri —
Hi @user, Just checking the participation criteria. Besides integrating Archestra, are there any specific constraints or guidelines we should follow (e.g., required features, demo expectations, judging criteria)?
Hello! I am trying to chat with my LLM, but it tells me "LLM Provider API key not configured. Please configure it in Chat Settings".
I have already configured a Mistral API key in the settings but it still throws me this error.
I checked the logs and it looks like its using Anthropic API by default. Is there a way to fix this?
Hello everyone,👋
Myself Harsh, a first-year undergraduate student.
I’m excited to participate in this hackathon and collaborate with the community.
I’m open to joining a team and eager to learn, contribute, and grow through this experience.
Looking forward to working with you all.
Adnan —
Hello can someone please send the link to there website
I see the roles/persmissions are defined at the archestra dashboard level, over what an user is able and not able to do. Is there a way, I can get it more workflow levels, for example, APIs for disabling access for a user to A2A Gateway or MCP Gateway or LLM Gateway?
I've set agent-mesh-tools__docker_status to *"Blocked"* in the Tool Policies page, but when I call it through the MCP Gateway, it still executes successfully.
*Setup:*
• Gateway: dac6e444-f791-423b-b724-4df4edae8182
• Profile: Default Profile
• Using Authorization Bearer token
• Endpoint: localhost:9000/v1/mcp/{gateway-id}
*Expected:* Policy violation error
*Actual:* Tool runs normally
Is there an additional step needed to enforce policies? Or should policies only apply to LLM Proxy calls, not direct MCP client calls?
Screenshots attached showing the blocked status in UI.
when using archestra, (e.g. in the archestra-openclaw example docker setup), do you always get the dual-llm-injection-prevention out of the box for every single request?
Hello everyone! Im finding my way around Archestra, its the first time Im using a tool like this. I wanted to install a Google Workspace MCP server, but I'm facing some issues. Is it supported?
I see MCP servers have recommended protocol of OAuth2.1. But if I were to try adding it to Archestra set up using Add MCP Server to the Private Registry, and select OAuth2.0; will the auth work as usual?
when you run the archestra/platform docker container, it seems to auto-start another container, kindest/node:v1.35.0, for the mcp control plane. this is an "interesting" pattern. i prefer having all my containers defined in docker-compose
Hi @user, Just checking the participation criteria. Besides integrating Archestra, are there any specific constraints or guidelines we should follow (e.g., required features, demo expectations, judging criteria)?