script_replace_persist

Persistently replace matching script responses.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/script-replace-persist.md

WHAT IT DOES

What script_replace_persist does on Jshookmcp

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

RISK

Why script_replace_persist is rated Medium

Modifies script behavior permanently; affects multiple executions irreversibly unless further changes made.

From the tool's definition Persistently replace matching script responses

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs script_replace_persist safely

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

script_replace_persist Rate-limited

script_replace_persist 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": {
    "script_replace_persist": {
      "limits": [
        {
          "counter": "script_replace_persist_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 Jshookmcp, apply this rule, and every script_replace_persist call is checked against it from then on.

FAQ

Questions about script_replace_persist

What does the script_replace_persist tool do? +

Persistently replace matching script responses. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on script_replace_persist? +

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

What risk level is script_replace_persist? +

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

Can I rate-limit script_replace_persist? +

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

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

script_replace_persist is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

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