list_local_event_hooks

List configured local event hooks and automation triggers.

Server Todos @hasna/todos
Category Read
Risk class Low
Parameters 00 required

What list_local_event_hooks does on Todos

AI agents call list_local_event_hooks to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_local_event_hooks needs a policy

This tool retrieves and displays existing event hooks and automation triggers. It performs a read-only query of the system's configuration state with no side effects, no code execution, and no data modification. The action is informational only.

From the tool's definition Tool name contains 'list' and description states 'List configured local event hooks and automation triggers' - a query operation that retrieves configuration data without modifying or executing anything.

Questions about list_local_event_hooks

What does the list_local_event_hooks tool do? +

List configured local event hooks and automation triggers. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_local_event_hooks? +

Register the Todos MCP server in PolicyLayer and add a rule for list_local_event_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 Todos. Nothing to install.

What risk level is list_local_event_hooks? +

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

Can I rate-limit list_local_event_hooks? +

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

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

list_local_event_hooks is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.