rename_project_app · Zion MCP: Risk & Policy

WHAT IT DOES

What rename_project_app does on Zion

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

PARAMETERS

Parameter	Type	Required
`appExId`	string	Yes
`appName`	string	Yes
`projectExId`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why rename_project_app needs a policy

This tool creates or modifies data reversibly by changing an app's name within a project. The change is not destructive (the app and its data remain intact), and it has limited blast radius since renaming is typically reversible through another rename operation. It does not delete, execute arbitrary code, or involve financial operations.

From the tool's definition Tool name 'rename_project_app' and description 'Rename an app inside a project' indicate modification of metadata/naming of an existing resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_project_app Rate-limited

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

FAQ

Questions about rename_project_app

What does the rename_project_app tool do? +

Rename an app inside a project. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does rename_project_app accept? +

rename_project_app accepts 3 parameters: appExId, appName, projectExId. Required: appExId, appName, projectExId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rename_project_app? +

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

What risk level is rename_project_app? +

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

Can I rate-limit rename_project_app? +

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

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

rename_project_app is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.