Inspect conflicts for candidate paths against active claims.
AI agents call coord_check_conflicts to retrieve information from Session Coord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and examines conflict data to inform the user about potential path conflicts in a coordination system. It has no side effects—it does not create claims, modify claims, delete claims, or execute external operations. It is a read-only inspection tool used to check the state of the system before taking action, making it a Read category risk.
From the tool's definition Tool name contains 'check' and description uses 'inspect', indicating a query/inspection operation with no modification. The purpose is to examine conflicts rather than resolve, modify, or delete them.
Attacks that exploit this kind of access
Inspect conflicts for candidate paths against active claims. It is categorised as a Read tool in the Session Coord MCP Server, which means it retrieves data without modifying state.
Register the Session Coord MCP server in PolicyLayer and add a rule for coord_check_conflicts: 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 Session Coord. Nothing to install.
coord_check_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coord_check_conflicts 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 coord_check_conflicts. 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.
coord_check_conflicts is provided by the Session Coord MCP server (lingfeng-vels/session-coord-mcp). 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 →