list_extension_workflows

List runtime-loaded extension workflows from plugins/ or workflows/ directories.

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

WHAT IT DOES

What list_extension_workflows does on Jshookmcp

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

Tool queries and retrieves workflow metadata without modifying systems or executing operations.

From the tool's definition List runtime-loaded extension workflows from plugins/ or workflows/ directories.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_extension_workflows Allowed

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

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

FAQ

Questions about list_extension_workflows

What does the list_extension_workflows tool do? +

List runtime-loaded extension workflows from plugins/ or workflows/ directories. 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 list_extension_workflows? +

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

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

Can I rate-limit list_extension_workflows? +

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

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

list_extension_workflows 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 →