Kullanıcıları ad, email, departman veya pozisyona göre arar
AI agents call search_users to retrieve information from MCP JSON Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation to retrieve user information based on filter criteria. It has no ability to create, modify, delete, or execute external operations. The capability to search users is a standard read operation with minimal blast radius—misuse would only expose already-stored user information, not cause data corruption or financial harm.
From the tool's definition Tool name 'search_users' and description 'searches users by name, email, department or position' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Kullanıcıları ad, email, departman veya pozisyona göre arar. It is categorised as a Read tool in the MCP JSON Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP JSON Database Server MCP server in PolicyLayer and add a rule for search_users: 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 JSON Database Server. Nothing to install.
search_users 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_users 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_users. 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_users is provided by the MCP JSON Database Server MCP server (yusuferenkt/mcp-database). 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 →