get_shell_completion
Generate bash, zsh, or fish completion script for todos CLI.
This record as markdown: /tools/todos/get-shell-completion.md
What get_shell_completion does on Todos
AI agents call get_shell_completion to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_shell_completion is rated Low
This tool retrieves and returns shell completion metadata/scripts without creating, modifying, deleting, or executing any substantive operations. It is a read-only utility that generates static completion data for CLI convenience.
From the tool's definition Tool generates completion scripts for CLI usage; the description explicitly states 'Generate bash, zsh, or fish completion script' with no modification or execution of tasks, files, or system state.
Attacks that exploit this kind of access
The rule that runs get_shell_completion safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_shell_completion, this is the rule to start with:
get_shell_completion 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 Todos, apply this rule, and every get_shell_completion call is checked against it from then on.
Questions about get_shell_completion
Generate bash, zsh, or fish completion script for todos CLI. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for get_shell_completion: 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.
get_shell_completion 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_shell_completion 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_shell_completion. 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_shell_completion 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.
This server
Across the catalogue