Search the database by reference number (allows partial matches).
AI agents call search_refnr to retrieve information from WatchBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from WatchBase's watch database without creating, modifying, or deleting any records. It performs a simple database search/filter operation, which is a classic Read operation. The blast radius of misuse is minimal—worst case an agent retrieves watch reference data, with no side effects or irreversible actions possible.
From the tool's definition Tool description explicitly states 'Search the database by reference number' with 'partial matches' capability. 'Search' is a query operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Search the database by reference number (allows partial matches). It is categorised as a Read tool in the WatchBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WatchBase MCP Server MCP server in PolicyLayer and add a rule for search_refnr: 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 WatchBase MCP Server. Nothing to install.
search_refnr 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 search_refnr 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 search_refnr. 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.
search_refnr is provided by the WatchBase MCP Server MCP server (watchdealer-pavel/watchbase-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 →