cc_name · Ttt MCP: Risk & Policy

WHAT IT DOES

What cc_name does on Ttt

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

This tool modifies existing data (a creature's name/nickname) in a reversible way. It creates or updates a label associated with a game entity. No code execution, deletion, or financial transaction is involved. The blast radius of misuse is minimal — at worst an unwanted nickname is assigned, which can presumably be changed again.

From the tool's definition Give a creature in your party a new nickname

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cc_name Rate-limited

cc_name 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_name": {
      "limits": [
        {
          "counter": "cc_name_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_name

What does the cc_name tool do? +

Give a creature in your party a new nickname. 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_name? +

Register the Ttt MCP server in PolicyLayer and add a rule for cc_name: 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_name? +

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

Can I rate-limit cc_name? +

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

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

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