score_record · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What score_record does on Sanka MCP Server

AI agents use score_record 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 score_record needs a policy

Scoring a record modifies its state by adding or updating a qualification score or rank. This is a reversible write operation (the score can be updated or removed), not a mere read (which would only retrieve scoring), not destructive (data is not deleted), and not execute/financial (no arbitrary code or money movement).

From the tool's definition Tool name 'score_record' and description stating it 'Score[s] a company or deal in Sanka' indicates modification of record data—specifically scoring/ranking fields.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

score_record Rate-limited

score_record 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": {
    "score_record": {
      "limits": [
        {
          "counter": "score_record_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 score_record

What does the score_record tool do? +

Score a company or deal in Sanka. Use this when the user wants qualification, prioritization, or an explanation of how a company or deal ranks. 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 score_record? +

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

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

Can I rate-limit score_record? +

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

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

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