extension_execute_in_context
Load an extension and execute a named exported context function.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/extension-execute-in-context.md
What extension_execute_in_context does on Jshookmcp
AI agents invoke extension_execute_in_context 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 extension_execute_in_context is rated High
Executes arbitrary code via extension loading and function invocation with unpredictable side effects.
From the tool's definition Load extension and execute named exported context function.
Attacks that exploit this kind of access
The rule that runs extension_execute_in_context 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 extension_execute_in_context, this is the rule to start with:
extension_execute_in_context 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 extension_execute_in_context call is checked against it from then on.
Questions about extension_execute_in_context
Load an extension and execute a named exported context function. 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 extension_execute_in_context: 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.
extension_execute_in_context 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 extension_execute_in_context 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 extension_execute_in_context. 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.
extension_execute_in_context 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