codecks_update_deck · Codecks MCP Server MCP: Risk & Policy

WHAT IT DOES

What codecks_update_deck does on Codecks MCP Server

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

WHY IT NEEDS A POLICY

Why codecks_update_deck needs a policy

This tool modifies existing data (a deck's title) in a reversible manner. The operation can be undone by renaming again. It does not create, delete, or execute external operations, placing it squarely in the Write category. The low severity reflects that renaming a deck has minimal blast radius—it affects organizational metadata with no cascading effects on core game development work or data loss risk.

From the tool's definition Tool description states 'Rename a deck by updating its title' - explicitly a modification operation that updates data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

codecks_update_deck Rate-limited

codecks_update_deck 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": {
    "codecks_update_deck": {
      "limits": [
        {
          "counter": "codecks_update_deck_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 Codecks MCP Server, so you can run agents against it safely.

FAQ

Questions about codecks_update_deck

What does the codecks_update_deck tool do? +

Rename a deck by updating its title. It is categorised as a Write tool in the Codecks 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 codecks_update_deck? +

Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_update_deck: 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 Codecks MCP Server. Nothing to install.

What risk level is codecks_update_deck? +

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

Can I rate-limit codecks_update_deck? +

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

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

codecks_update_deck is provided by the Codecks MCP Server MCP server (microkorg/codecks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.