Detect conflicting priorities and resource constraints.
AI agents call detect_conflicts to retrieve information from Quarterback without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs conflict detection and analysis on existing project data—a read-only operation that queries state without side effects. It does not create, modify, delete, or execute external actions. The severity is low because misuse would only surface incorrect analysis, not cause data loss or unintended operations.
From the tool's definition Tool name 'detect_conflicts' and description 'Detect conflicting priorities and resource constraints' indicate analysis and retrieval of conflict information with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Detect conflicting priorities and resource constraints. It is categorised as a Read tool in the Quarterback MCP Server, which means it retrieves data without modifying state.
Register the Quarterback MCP server in PolicyLayer and add a rule for detect_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 Quarterback. Nothing to install.
detect_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 detect_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 detect_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.
detect_conflicts is provided by the Quarterback MCP server (bobbyrgoldsmith/quarterback). 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 →