New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

extension_execute_in_context

Load an extension and execute a named exported context function.

SERVERJshookmcp SOURCE@jshookmcp/jshook
High RISK CLASS
Category Execute
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/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.

Questions about extension_execute_in_context

What does the extension_execute_in_context tool do? +

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.

How do I enforce a policy on extension_execute_in_context? +

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.

What risk level is extension_execute_in_context? +

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

Can I rate-limit extension_execute_in_context? +

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.

How do I block extension_execute_in_context completely? +

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.

What MCP server provides extension_execute_in_context? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Jshook's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.