update_slip · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_slip does on Sanka MCP Server

AI agents use update_slip 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 IT NEEDS A POLICY

Why update_slip needs a policy

The tool modifies existing records ('slip') in the Sanka system without permanently deleting or destroying data. This is a classic Write operation. Severity is medium because updates to business records like slips could have operational impact, but the effect depends on what fields are modified and the context of use.

From the tool's definition Tool name 'update_slip' and description 'Update an existing slip in Sanka' indicate modification of existing data. The action is reversible (updates can be undone with subsequent updates), distinguishing it from destructive operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_slip Rate-limited

update_slip 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_slip": {
      "limits": [
        {
          "counter": "update_slip_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_slip

What does the update_slip tool do? +

Update an existing slip in Sanka. 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_slip? +

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

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

Can I rate-limit update_slip? +

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

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

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