AI agents call check_contradictions to retrieve information from Axiom-hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or analyzes decision memory to detect contradictions—a read-only query operation with no side effects. It supports the server's core function of enforcing architectural consistency by checking prior decisions against current context. Confidence is not higher due to empty description, but the naming pattern and architectural role are clear.
From the tool's definition Tool name 'check_contradictions' combined with server's purpose of 'contradiction detection' and sibling tools like 'check_constraints', 'get_board_items', 'get_decision_timeline' which are all read operations.
Attacks that exploit this kind of access
check_contradictions. It is categorised as a Read tool in the Axiom-hub MCP Server, which means it retrieves data without modifying state.
Register the Axiom-hub MCP server in PolicyLayer and add a rule for check_contradictions: 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 Axiom-hub. Nothing to install.
check_contradictions 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 check_contradictions 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 check_contradictions. 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.
check_contradictions is provided by the Axiom-hub MCP server (varunajaytawde28-design/smm-sync). 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 →