AI agents call list_hands to retrieve information from Kontexta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/enumeration tool that retrieves metadata about registered command tools. It has no side effects, does not execute commands, does not modify data, and does not delete anything. It is purely informational, fitting the Read category with low severity since an AI agent misusing it would only gain visibility into available tools without triggering any actions.
From the tool's definition Tool name is 'list_hands' and description states it 'List[s] every Hands command tool currently registered' with metadata retrieval only (project scope, tool name, danger level, confirmation flag, description).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every Hands command tool currently registered, with project scope, tool name, danger level, confirmation flag, and description. Hands tools come from per-project. It is categorised as a Read tool in the Kontexta MCP Server, which means it retrieves data without modifying state.
Register the Kontexta MCP server in PolicyLayer and add a rule for list_hands: 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 Kontexta. Nothing to install.
list_hands 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 list_hands 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 list_hands. 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.
list_hands is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →