Contest the proposed resolution
AI agents use contest_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.
This tool writes/updates the state of a coordination process (contesting a resolution), which is a reversible modification to workflow state. It does not execute code, delete data, or involve finances. The blast radius is medium since contesting a resolution in a multi-agent coordination system could cause workflow disruption or stall work across sessions, but it is reversible.
From the tool's definition Contest the proposed resolution — modifies the state of a conflict resolution workflow by rejecting or challenging a proposed resolution.
Attacks that exploit this kind of access
Contest 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 contest_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.
contest_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 contest_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 contest_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.
contest_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.
contest_resolution is one line of Mcp Coordinator's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →