AI agents use resolve_contradiction to create or update resources in Axiom-hub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Axiom-hub environment.
The tool name and server context indicate this performs conflict resolution by modifying stored contradictions in the decision memory system. This is a reversible Write operation (updating/modifying state) rather than Read (it changes data), Execute (no code execution), Destructive (resolvable), or Financial (no money involved).
From the tool's definition Tool name 'resolve_contradiction' and context indicate it modifies decision memory state. Server description states 'Human resolves conflicts on a dashboard or in chat', suggesting this tool implements that conflict resolution, which involves updating the…
Attacks that exploit this kind of access
resolve_contradiction. It is categorised as a Write tool in the Axiom-hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Axiom-hub MCP server in PolicyLayer and add a rule for resolve_contradiction: 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.
resolve_contradiction 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 resolve_contradiction 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 resolve_contradiction. 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.
resolve_contradiction 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 →