Approve or deny an action.
AI agents invoke approval_resolve to trigger actions in AIOS Co-Founder MCP. 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.
This tool controls the approval gating mechanism described in the server description for 'sensitive operations.' Resolving an approval can trigger any downstream action (e.g., sending emails, modifying calendar events, updating contacts). The actual effect depends on what was gated, but the act of approving/denying directly enables execution of those sensitive operations.
From the tool's definition 'Approve or deny an action' — resolves a pending approval gate, triggering or blocking a downstream operation
Attacks that exploit this kind of access
Approve or deny an action. It is categorised as a Execute tool in the AIOS Co-Founder MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AIOS Co-Founder MCP server in PolicyLayer and add a rule for approval_resolve: 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 AIOS Co-Founder MCP. Nothing to install.
approval_resolve 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 approval_resolve 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 approval_resolve. 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.
approval_resolve is provided by the AIOS Co-Founder MCP server (varun-b-nagaraj/python-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 →