AI agents call search_calls 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.
The search_calls tool retrieves or queries call data based on provided criteria. This is a read-only operation with no side effects on data integrity, no code execution, and no financial impact. It returns matching records but does not create, modify, or delete any data. Severity is low because misuse would only expose data visibility, not cause operational harm or irreversible changes.
From the tool's definition Tool name and description indicate 'Search for calls using flexible criteria' — a query operation that retrieves call records without modifying, deleting, or executing external actions.
Documented attack patterns abuse exactly the kind of access search_calls 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_calls:
{
"version": "1",
"default": "deny",
"tools": {
"search_calls": {}
}
}search_calls 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 calls 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_calls: 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_calls 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_calls 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_calls. 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_calls 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.