AI agents call search_cases to retrieve information from EspoCRM-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search/query operation that retrieves support case records. It performs no modifications, deletions, executions, or financial transactions. The flexible criteria allow filtering but do not alter data. Classification as Read is appropriate with low severity since read access to cases carries minimal risk compared to destructive or financial operations.
From the tool's definition Tool name 'search_cases' and description 'Search for support cases using flexible criteria' indicate a query/retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access search_cases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EspoCRM-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_cases:
{
"version": "1",
"default": "deny",
"tools": {
"search_cases": {}
}
}search_cases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for support cases using flexible criteria. It is categorised as a Read tool in the EspoCRM-MCP MCP Server, which means it retrieves data without modifying state.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for search_cases: 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 EspoCRM-MCP. Nothing to install.
search_cases 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_cases 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_cases. 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_cases is provided by the EspoCRM- MCP server (zaphod-black/espomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 EspoCRM-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
46 EspoCRM-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.