render.scale · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What render.scale does on MCP Fullstack

AI agents invoke render.scale 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.scale needs a policy

Scaling a service executes infrastructure changes that modify running systems and resource consumption. While not destructive (reversible by scaling down) or financial (no direct money movement), this is Execute-level because it triggers consequential external operations on deployed infrastructure.

From the tool's definition Tool name is 'render.scale' with description 'Scale a service'. In deployment/operations contexts, scaling a service triggers external operations (horizontal/vertical scaling, resource allocation, container orchestration) whose effects depend on the scaling…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render.scale Rate-limited

render.scale 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.scale": {
      "limits": [
        {
          "counter": "render.scale_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.scale

What does the render.scale tool do? +

Scale a 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.scale? +

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for render.scale: 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.scale? +

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

Can I rate-limit render.scale? +

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

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

render.scale 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.