extension_list_installed

List installed extensions from the local registry.

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/extension-list-installed.md

WHAT IT DOES

What extension_list_installed does on Jshookmcp

AI agents call extension_list_installed 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 extension_list_installed is rated Low

Retrieves data about installed extensions without modifying or executing anything.

From the tool's definition List installed extensions from the local registry.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

extension_list_installed Allowed

extension_list_installed 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": {
    "extension_list_installed": {}
  }
}

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 extension_list_installed call is checked against it from then on.

FAQ

Questions about extension_list_installed

What does the extension_list_installed tool do? +

List installed extensions from the local registry. 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 extension_list_installed? +

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

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

Can I rate-limit extension_list_installed? +

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

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

extension_list_installed 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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