archive_custom_object_record · Sanka MCP Server MCP

WHAT IT DOES

What archive_custom_object_record does on Sanka MCP Server

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

Archiving is a data modification operation that changes record status/visibility but explicitly does not permanently delete data, making it reversible. This distinguishes it from Destructive (which would be irreversible deletion). It is Write-category because it modifies data state.

From the tool's definition Tool description states: 'Archive a Sanka custom object row by row UUID. This is a soft archive, not a permanent delete.' The operation modifies data state by marking records as archived, which is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_custom_object_record Rate-limited

archive_custom_object_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": {
    "archive_custom_object_record": {
      "limits": [
        {
          "counter": "archive_custom_object_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 archive_custom_object_record

What does the archive_custom_object_record tool do? +

Archive a Sanka custom object row by row UUID. This is a soft archive, not a permanent delete. 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 archive_custom_object_record? +

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

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

Can I rate-limit archive_custom_object_record? +

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

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

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