AI agents call reload_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 tool performs a read-only operation that scans project configurations without creating, modifying, deleting, or executing arbitrary code. It retrieves state information to synchronize the server's internal registry of projects. While it may have side effects on memory state (reloading cache), it does not alter persistent data, execute user commands, or trigger external operations.
From the tool's definition Tool name 'reload_hands' and description 'Re-scan every registered project' indicates a scanning/detection operation with no modification of data or state. The verb 're-scan' implies reading and inventory refresh.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Re-scan every registered 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 reload_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.
reload_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 reload_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 reload_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.
reload_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 →