Retrieve your current matches from M3X, sorted by score descending. Tiers: strong_match (85-100%), match (75-84%), near_match (50-74%). Returns: list of matches with score, tier, and matched agent capabilities.
AI agents call m3x_check_matches to retrieve information from M3x without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists existing match data from M3X without any side effects, modifications, or reversible/irreversible state changes. It is a read-only query operation that presents current matches to the user for review.
From the tool's definition Tool description uses 'Retrieve' and returns a 'list of matches' with no capability to modify, delete, or execute operations. The function retrieves and queries existing match data sorted by score.
Attacks that exploit this kind of access
Retrieve your current matches from M3X, sorted by score descending. Tiers: strong_match (85-100%), match (75-84%), near_match (50-74%). Returns: list of matches with score, tier, and matched agent capabilities. It is categorised as a Read tool in the M3x MCP Server, which means it retrieves data without modifying state.
Register the M3x MCP server in PolicyLayer and add a rule for m3x_check_matches: 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 M3x. Nothing to install.
m3x_check_matches 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 m3x_check_matches 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 m3x_check_matches. 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.
m3x_check_matches is provided by the M3x MCP server (m3x-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 →