Low Risk

list_plugin_clients

List connected JiShi plugin clients for multiplexing.

Part of the Jishi MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call list_plugin_clients to retrieve information from Jishi without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_plugin_clients only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

jishi.yaml
tools:
  list_plugin_clients:
    rules:
      - action: allow

See the full Jishi policy for all 7 tools.

Tool Name list_plugin_clients
Category Read
MCP Server Jishi MCP Server
Risk Level Low

Agents calling read-class tools like list_plugin_clients have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the list_plugin_clients tool do? +

List connected JiShi plugin clients for multiplexing.. It is categorised as a Read tool in the Jishi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_plugin_clients? +

Add a rule in your Intercept YAML policy under the tools section for list_plugin_clients. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Jishi MCP server.

What risk level is list_plugin_clients? +

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

Can I rate-limit list_plugin_clients? +

Yes. Add a rate_limit block to the list_plugin_clients rule in your Intercept 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_plugin_clients completely? +

Set action: deny in the Intercept policy for list_plugin_clients. 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_plugin_clients? +

list_plugin_clients is provided by the Jishi MCP server (@jiujiang/jishi-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Jishi

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.