ast_transform_apply
Apply transforms to input code or a live page scriptId.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/ast-transform-apply.md
What ast_transform_apply does on Jshookmcp
AI agents invoke ast_transform_apply to trigger actions in Jshookmcp. 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 ast_transform_apply is rated High
Applies arbitrary code transforms to live pages or input code, enabling script injection and execution.
From the tool's definition Apply transforms to input code or live page scriptId
Attacks that exploit this kind of access
The rule that runs ast_transform_apply 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 ast_transform_apply, this is the rule to start with:
ast_transform_apply 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every ast_transform_apply call is checked against it from then on.
Questions about ast_transform_apply
Apply transforms to input code or a live page scriptId. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for ast_transform_apply: 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.
ast_transform_apply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ast_transform_apply 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.
Set action: deny in the PolicyLayer policy for ast_transform_apply. 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.
ast_transform_apply 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.
More on Jshook, and thousands of servers like it.
Across the catalogue