get_custom_hooks
[MAINTENANCE] 273287cb — list a project's user-defined hooks (newest first). Optional event filter and enabled_only flag. Each entry includes the derived slug (the filename stem used when written to .claude/hooks/) alongside the stored fields.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-custom-hooks.md
What get_custom_hooks does on Meridian
AI agents call get_custom_hooks to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
event | string | — | Optional filter to only this event's hooks. |
project_id | string | — | |
enabled_only | boolean | — | When true, only return hooks with enabled=true. |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
Parameters from the server's own tool schema.
Why get_custom_hooks is rated Low
This tool retrieves configuration data about user-defined hooks without modifying, deleting, or executing anything. The optional filters (event, enabled_only) are query parameters that don't affect stored state. The blast radius of misuse is minimal—an AI could learn hook configurations but cannot invoke them or change them, only read their metadata. Classified as Read with low severity.
From the tool's definition 'list a project's user-defined hooks' — retrieves and queries hook metadata with no modification. The tool returns stored fields and derived slugs for informational purposes only.
Attacks that exploit this kind of access
The rule that runs get_custom_hooks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_custom_hooks, this is the rule to start with:
get_custom_hooks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_custom_hooks call is checked against it from then on.
Questions about get_custom_hooks
[MAINTENANCE] 273287cb — list a project's user-defined hooks (newest first). Optional event filter and enabled_only flag. Each entry includes the derived slug (the filename stem used when written to .claude/hooks/) alongside the stored fields. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_custom_hooks accepts 4 parameters: event, project_id, enabled_only, project_name. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_custom_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 Meridian. Nothing to install.
get_custom_hooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_custom_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.
Set action: deny in the PolicyLayer policy for get_custom_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.
get_custom_hooks is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue