list_plugin_hooks

THE RISK

Low Risk

Why list_plugin_hooks needs a policy

This tool retrieves information about registered hooks without creating, modifying, or deleting any data. It is a read-only introspection operation on the plugin system's configuration. The blast radius of misuse is minimal—an agent could only learn about hook structure, not alter system behavior or access sensitive data beyond hook metadata.

From the tool's definition Tool name 'list_plugin_hooks' and description 'Show registered hooks' indicate a query/retrieval operation with no modification capability.

Documented attack patterns abuse exactly the kind of access list_plugin_hooks gives an agent:

POLICY

How to control list_plugin_hooks

PolicyLayer is an MCP gateway — it sits between your AI agents and Project Tessera, and nothing reaches the server without passing your rules. This is the rule we recommend for list_plugin_hooks:

policy.json

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

list_plugin_hooks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Project Tessera — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Project Tessera tools

Execute migrate_data Run data migration. Write organize_files Organize files in the workspace. Write sync_documents Incremental sync — only new/changed/deleted files. Write toggle_auto_learn Toggle or check auto-learning on/off. Write digest_conversation Extract and save knowledge from the current session. Write import_conversations Import conversations and extract knowledge. Write import_from_ai Import memories from another AI tool's export. Write learn Save and immediately index new knowledge.

All 43 Project Tessera tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about list_plugin_hooks

What does the list_plugin_hooks tool do? +

Show registered hooks. It is categorised as a Read tool in the Project Tessera MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_plugin_hooks? +

Register the Project Tessera MCP server in PolicyLayer and add a rule for list_plugin_hooks: 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 Project Tessera. Nothing to install.

What risk level is list_plugin_hooks? +

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

Can I rate-limit list_plugin_hooks? +

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

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

list_plugin_hooks is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Project Tessera tool call.

Start from Project Tessera, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →