rename_instance

Set (or clear) a subscribed instance

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/rename-instance.md

WHAT IT DOES

What rename_instance does on ProAgentStore

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

RISK

Why rename_instance is rated Medium

Modifies instance metadata (name/subscription state) reversibly without permanent data loss or code execution.

From the tool's definition rename_instance: Set (or clear) a subscribed instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_instance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_instance, this is the rule to start with:

rename_instance Rate-limited

rename_instance 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_instance": {
      "limits": [
        {
          "counter": "rename_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every rename_instance call is checked against it from then on.

FAQ

Questions about rename_instance

What does the rename_instance tool do? +

Set (or clear) a subscribed instance. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_instance? +

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

What risk level is rename_instance? +

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

Can I rate-limit rename_instance? +

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

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

rename_instance is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →