codecks_rename_space · Codecks MCP Server MCP: Risk & Policy

WHAT IT DOES

What codecks_rename_space does on Codecks MCP Server

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

Renaming a space modifies project structure and organization metadata reversibly—users can rename it again to correct mistakes. This is a Write operation (modification without deletion). Severity is medium because incorrect renames could disrupt team workflows and collaboration if the AI renames spaces inappropriately, but the action is fully reversible and does not destroy data or cause financial impact.

From the tool's definition Tool name 'codecks_rename_space' and description 'Rename a space in a project' indicate modification of existing project metadata. This changes a space's name but is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

codecks_rename_space Rate-limited

codecks_rename_space 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_rename_space": {
      "limits": [
        {
          "counter": "codecks_rename_space_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_rename_space

What does the codecks_rename_space tool do? +

Rename a space in a project. 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_rename_space? +

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

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

Can I rate-limit codecks_rename_space? +

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

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

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