AI agents call get_record_by_id to retrieve information from 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 a specific record from the Zoho CRM system by its identifier. It performs a query operation with no side effects—it does not create, modify, delete, or execute arbitrary code. The operation is read-only and returns data without altering system state. The low severity reflects the minimal blast radius of misuse, as retrieval alone cannot cause data loss or unintended modifications.
From the tool's definition Tool name 'get_record_by_id' and description 'Get a specific record by its ID' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_record_by_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_record_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_record_by_id": {}
}
}get_record_by_id 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.
Get a specific record by its ID. It is categorised as a Read tool in the MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the MCP-Server MCP server in PolicyLayer and add a rule for get_record_by_id: 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-Server. Nothing to install.
get_record_by_id 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_record_by_id 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_record_by_id. 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_record_by_id is provided by the MCP-Server MCP server (officehub-tech-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.