get_matches
AI agents call get_matches to retrieve information from MCP-Networkbot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_matches' follows the Read category pattern (get + retrieval). In the context of a networking platform, 'matches' likely refers to matched connections or profiles. The empty description reduces confidence, but the naming convention and sibling tools strongly suggest this retrieves network matches without modifying data. No evidence of execution, financial activity, or destructive operations.
From the tool's definition Tool name 'get_matches' indicates a retrieval operation. The description is empty, limiting evidence, but the verb 'get' and context of a networking platform suggest data retrieval without side effects.
Attacks that exploit this kind of access
get_matches. It is categorised as a Read tool in the MCP-Networkbot MCP Server, which means it retrieves data without modifying state.
Register the MCP-Networkbot 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 MCP-Networkbot. 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 MCP-Networkbot MCP server (kunalkhanna2007-sys/networkbot-python). 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 →