Activate a specific Worksona agent to handle a request
AI agents invoke activate_agent to trigger actions in Worksona MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Activating an agent causes it to run and take actions autonomously. Since the agent could perform a wide range of operations (development, business workflows, multi-agent coordination) depending on what it's told to do, this is an Execute-category tool. The blast radius is high because the activated agent may itself trigger write, destructive, or other impactful operations as part of its task.
From the tool's definition 'Activate a specific Worksona agent to handle a request' — triggers execution of an external AI agent to perform operations
Attacks that exploit this kind of access
Activate a specific Worksona agent to handle a request. It is categorised as a Execute tool in the Worksona MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Worksona MCP Server MCP server in PolicyLayer and add a rule for activate_agent: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Worksona MCP Server. Nothing to install.
activate_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the activate_agent rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for activate_agent. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
activate_agent is provided by the Worksona MCP Server MCP server (worksona/-worksona-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →