New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_estimate

Update an existing estimate in Sanka. Attach uploaded file ids with

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/update-estimate.md

What update_estimate does on Sanka MCP Server

AI agents use update_estimate to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

Why update_estimate is rated Medium

This tool modifies an existing estimate record reversibly—changes can be undone or overwritten through subsequent updates. It does not delete data (which would be Destructive) nor does it commit financial obligations (Financial), but it does alter business-critical data.

From the tool's definition Tool name is 'update_estimate' and description states 'Update an existing estimate in Sanka.' The verb 'update' indicates modification of existing data. The ability to 'attach uploaded file ids' suggests the tool can modify record state and attachments.

Questions about update_estimate

What does the update_estimate tool do? +

Update an existing estimate in Sanka. Attach uploaded file ids with. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_estimate? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_estimate? +

update_estimate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_estimate? +

Yes. Add a rate_limit block to the update_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.

How do I block update_estimate completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_estimate? +

update_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.

More on Sanka MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.