browse_extension_registry

Browse the online extension registry for installable plugins and workflows.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/browse-extension-registry.md

WHAT IT DOES

What browse_extension_registry does on Jshookmcp

AI agents call browse_extension_registry to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browse_extension_registry is rated Low

Retrieves and queries extension registry data without modifying or executing anything.

From the tool's definition Browse online extension registry for installable plugins and workflows

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browse_extension_registry 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 browse_extension_registry, this is the rule to start with:

browse_extension_registry Allowed

browse_extension_registry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browse_extension_registry": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every browse_extension_registry call is checked against it from then on.

FAQ

Questions about browse_extension_registry

What does the browse_extension_registry tool do? +

Browse the online extension registry for installable plugins and workflows. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_extension_registry? +

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

browse_extension_registry is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browse_extension_registry? +

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

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

browse_extension_registry 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →