Approve the proposed resolution
AI agents use approve_resolution to create or update resources in Mcp Coordinator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Coordinator environment.
Approving a resolution modifies the state of a conflict-resolution record, committing a decision about file claims across sessions. This is a reversible state change (a write/update action) rather than destructive or financial. Misuse could cause incorrect conflict resolutions, forcing wrong file ownership assignments across AI coding agents, hence medium severity.
From the tool's definition 'Approve the proposed resolution' — confirms or accepts a coordination decision in the multi-session conflict resolution workflow
Attacks that exploit this kind of access
Approve the proposed resolution. It is categorised as a Write tool in the Mcp Coordinator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Coordinator MCP server in PolicyLayer and add a rule for approve_resolution: 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 Mcp Coordinator. Nothing to install.
approve_resolution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the approve_resolution 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 approve_resolution. 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.
approve_resolution is provided by the Mcp Coordinator MCP server (swoofer/mcp-coordinator). 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 →