update_script · MCPMake MCP: Risk & Policy

WHAT IT DOES

What update_script does on MCPMake

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

WHY IT NEEDS A POLICY

Why update_script needs a policy

This tool modifies existing script metadata and schemas reversibly. While it doesn't execute code or delete scripts, it changes the configuration and analysis of scripts, which can affect subsequent executions. It falls under Write rather than Execute because the tool itself performs analysis/metadata updates, not code execution.

From the tool's definition Tool name is 'update_script' and description states 'Re-analyze a script to update its schema and metadata', indicating modification of script metadata and schema definitions without deletion or execution of the script itself.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_script Rate-limited

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

FAQ

Questions about update_script

What does the update_script tool do? +

Re-analyze a script to update its schema and metadata. It is categorised as a Write tool in the MCPMake MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_script? +

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

What risk level is update_script? +

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

Can I rate-limit update_script? +

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

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

update_script is provided by the MCPMake MCP server (shex1627/mcpmake). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.