Get all results after all items have been processed. This tool will return an error if processing is not complete.
AI agents call get_all_results to retrieve information from Loop MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously computed or stored results without modifying, deleting, or executing anything. It is purely a read operation that queries the internal state of the loop processor and returns accumulated results. No data is created, modified, destroyed, or financial transactions occur.
From the tool's definition Tool name 'get_all_results' and description 'Get all results' indicates retrieval of stored data with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all results after all items have been processed. This tool will return an error if processing is not complete. It is categorised as a Read tool in the Loop MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Loop MCP Server MCP server in PolicyLayer and add a rule for get_all_results: 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 Loop MCP Server. Nothing to install.
get_all_results 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_all_results 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_all_results. 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_all_results is provided by the Loop MCP Server MCP server (smogili1/loop_mcp). 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 →