AI agents call mtrkr_companion_compare to retrieve information from Mtrkr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming pattern and the sibling tools (mtrkr_companion_analyze, mtrkr_companion_get, mtrkr_inspect_address, mtrkr_security_scan), this tool appears to be part of a wallet intelligence/analysis suite that retrieves and analyzes blockchain data without modifying state. The '_companion' prefix and 'compare' verb suggest read-only comparison operations.
From the tool's definition Tool name 'mtrkr_companion_compare' suggests comparison/analysis of data. The description is empty, providing no explicit details about functionality.
Attacks that exploit this kind of access
mtrkr_companion_compare. It is categorised as a Read tool in the Mtrkr MCP Server, which means it retrieves data without modifying state.
Register the Mtrkr MCP server in PolicyLayer and add a rule for mtrkr_companion_compare: 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 Mtrkr. Nothing to install.
mtrkr_companion_compare 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 mtrkr_companion_compare 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 mtrkr_companion_compare. 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.
mtrkr_companion_compare is provided by the Mtrkr MCP server (mtrkr-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 →