AI agents call detect_conflicts to retrieve information from Odgs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, classification relies on the name 'detect_conflicts' and server context. The ODGS server performs deterministic governance checking and produces signed certificates. A 'detect_conflicts' tool most likely analyzes or reports on conflicts in rules or compliance state—a read operation.
From the tool's definition Tool named 'detect_conflicts' with empty description. Based on name and context within a governance validation engine, it appears to query or identify conflicts in regulatory rules or bindings rather than modify, execute external operations, or delete data.
Attacks that exploit this kind of access
detect_conflicts. It is categorised as a Read tool in the Odgs MCP Server, which means it retrieves data without modifying state.
Register the Odgs 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 Odgs. 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 Odgs MCP server (metricprovenance/odgs-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 →