Load one estimate from Sanka by estimate id, numeric id, or external reference.
AI agents call get_estimate to retrieve information from Sanka MCP 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 simple data retrieval operation to fetch an estimate record from the Sanka system. It takes an identifier as input and returns the corresponding estimate data. There is no mention of creating, modifying, deleting, or executing any operations. The action is read-only with no side effects, placing it squarely in the Read category.
From the tool's definition Tool name is "get_estimate" and description states "Load one estimate from Sanka by estimate id, numeric id, or external reference." The verb "load" indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Load one estimate from Sanka by estimate id, numeric id, or external reference. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_estimate: 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 Sanka MCP Server. Nothing to install.
get_estimate 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_estimate 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_estimate. 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_estimate is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). 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 →