New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

install_local_extension

Install or update a local workflow extension from a manifest, directory, or offline bundle.

SERVERTodos SOURCE@hasna/todos
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/install-local-extension.md

What install_local_extension does on Todos

AI agents invoke install_local_extension to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why install_local_extension is rated High

Installing or updating extensions executes system-level operations that modify the runtime environment. This goes beyond a simple write (data modification) — it deploys executable code/workflows that can alter system behavior. An AI agent misusing this could install malicious or unintended extensions with potentially broad impact on the system's behavior.

From the tool's definition "Install or update a local workflow extension from a manifest, directory, or offline bundle"

Questions about install_local_extension

What does the install_local_extension tool do? +

Install or update a local workflow extension from a manifest, directory, or offline bundle. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_local_extension? +

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

install_local_extension is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_local_extension? +

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

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

install_local_extension 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.

More on Todos, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todos's. Pull the full record:

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.