update_company

Update an existing company. Default target=

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-company.md

WHAT IT DOES

What update_company does on Sanka MCP Server

AI agents use update_company 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.

RISK

Why update_company is rated Medium

The tool modifies company records which is a Write operation—data is being changed but not deleted. Severity is medium because updating company information could affect business operations, user access, or linked records, but the effect is reversible.

From the tool's definition Tool name 'update_company' and description 'Update an existing company' indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_company safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_company, this is the rule to start with:

update_company Rate-limited

update_company stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_company": {
      "limits": [
        {
          "counter": "update_company_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every update_company call is checked against it from then on.

FAQ

Questions about update_company

What does the update_company tool do? +

Update an existing company. Default target=. 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_company? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_company: 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_company? +

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

Can I rate-limit update_company? +

Yes. Add a rate_limit block to the update_company 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_company completely? +

Set action: deny in the PolicyLayer policy for update_company. 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_company? +

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

KEEP EXPLORING

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

This server

All 349 Sanka MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →