cc_retire · Ttt MCP: Risk & Policy

WHAT IT DOES

What cc_retire does on Ttt

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

WHY IT NEEDS A POLICY

Why cc_retire needs a policy

This tool modifies game state by moving a creature entity to a resting location, but the action is reversible and has no destructive intent. It does not delete data, execute arbitrary code, or cause financial effects. It is a Write operation within the game's rule system—changing a creature's status/location persistently but without permanent loss.

From the tool's definition Tool description states 'Send a creature home to Millhaven to rest', which is a state-modifying action that changes creature status/location.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cc_retire Rate-limited

cc_retire 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": {
    "cc_retire": {
      "limits": [
        {
          "counter": "cc_retire_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 Ttt, so you can run agents against it safely.

FAQ

Questions about cc_retire

What does the cc_retire tool do? +

Send a creature home to Millhaven to rest. Only available once their bond reaches 70. It is categorised as a Write tool in the Ttt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cc_retire? +

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

What risk level is cc_retire? +

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

Can I rate-limit cc_retire? +

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

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

cc_retire is provided by the Ttt MCP server (srmtech-git/mcparcade). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.