AI agents call predict.matched-pairs to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns market data (price spreads across venues) for human decision-making. It performs no write operations, does not execute trades, does not delete data, and does not commit financial transactions. While the server operates in a financial domain (USDC settlement), this specific tool is purely informational—it surfaces arbitrage opportunities but leaves execution to other agents/users.
From the tool's definition Tool name 'predict.matched-pairs' and description indicate it 'retrieves...market pairs...with price spread' for analysis. Words like 'spotting' and '(heuristic)' signal query/comparison functionality with no modification or execution of trades.
Attacks that exploit this kind of access
Cross-venue equivalent market pairs (same question on Polymarket vs Kalshi) with price spread for arbitrage spotting (heuristic). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for predict.matched-pairs: 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 Mcp. Nothing to install.
predict.matched-pairs 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 predict.matched-pairs 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 predict.matched-pairs. 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.
predict.matched-pairs is provided by the MCP server (@2sio/mcp). 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 →