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.dac6e444-f791-423b-b724-4df4edae8182localhost:9000/v1/mcp/{gateway-id}/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.”
👋 Hi everyone, I’m Tushar. Looking forward to hacking together and learning from you all. Great to meet the community!
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!profile permissions. So if someone has profile: read, they can see all three. If they have profile: create , they can create any of them. There's no separate permission per gateway type which is something on our radar.profile permissions through API? I don't see an appropriate API endpoint to do this? Is there a different way to do it?PUT /api/roles/<roleId>, for example: Authorization: <your-api-key>
Content-Type: application/json
{
"permission": {
"profile": ["create", "read"],
"tool": ["read"]
}
}```
Here's our API reference <https://archestra.ai/docs/platform-api-reference>
and docs around access control: <https://archestra.ai/docs/platform-access-control>