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

instrumentation_hook_preset

Apply hook presets inside an instrumentation session.

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/instrumentation-hook-preset.md

What instrumentation_hook_preset does on Jshookmcp

AI agents invoke instrumentation_hook_preset 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 instrumentation_hook_preset is rated High

Applies instrumentation hooks at runtime, triggering external operations with potentially wide impact.

From the tool's definition Apply hook presets inside an instrumentation session

Questions about instrumentation_hook_preset

What does the instrumentation_hook_preset tool do? +

Apply hook presets inside an instrumentation session. 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 instrumentation_hook_preset? +

Register the Jshook MCP server in PolicyLayer and add a rule for instrumentation_hook_preset: 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 instrumentation_hook_preset? +

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

Can I rate-limit instrumentation_hook_preset? +

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

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

instrumentation_hook_preset 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.