render.redeploy · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What render.redeploy does on MCP Fullstack

AI agents invoke render.redeploy to trigger actions in MCP Fullstack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why render.redeploy needs a policy

Redeploying a service is an external operation that restarts/rebuilds a running production service. It is not purely data write or read; it executes an infrastructure action with significant blast radius (service downtime, running code changes). It does not permanently destroy data, so Destructive is not the best fit, but Execute captures the side-effectful nature of triggering a live deployment pipeline.

From the tool's definition 'Redeploy a Render service' — triggers an external deployment operation on a live service

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render.redeploy Rate-limited

render.redeploy stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "render.redeploy": {
      "limits": [
        {
          "counter": "render.redeploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Fullstack, so you can run agents against it safely.

FAQ

Questions about render.redeploy

What does the render.redeploy tool do? +

Redeploy a Render service. It is categorised as a Execute tool in the MCP Fullstack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on render.redeploy? +

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

What risk level is render.redeploy? +

render.redeploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit render.redeploy? +

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

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

render.redeploy is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.