Return PERSISTED matches for this profile_version (no recompute).
AI agents call get_matches to retrieve information from Bandiradar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns pre-calculated matches stored in a database or cache for a given profile version. It performs a read-only query operation with no capacity to create, modify, delete, or execute operations. The lowest blast radius applies: an AI agent misusing this tool can only access information already persisted in the system, not alter state or trigger external operations.
From the tool's definition Tool description states 'Return PERSISTED matches' — a retrieval operation with no side effects. The verb 'return' and the qualifier 'no recompute' indicate this tool queries and reads previously computed results without modification or execution.
Attacks that exploit this kind of access
Return PERSISTED matches for this profile_version (no recompute). It is categorised as a Read tool in the Bandiradar MCP Server, which means it retrieves data without modifying state.
Register the Bandiradar MCP server in PolicyLayer and add a rule for get_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 Bandiradar. Nothing to install.
get_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 get_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 get_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.
get_matches is provided by the Bandiradar MCP server (mayai-it/bandiradar). 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 →