Get results for all completed and failed tasks in a batch.
AI agents call get_batch_results to retrieve information from Hive 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 results from completed or failed tasks within a batch. It performs a query operation that reads data without creating, modifying, deleting, or executing any operations. The action is purely informational and has no blast radius if misused by an AI agent—it cannot cause harm beyond potentially exposing batch result data.
From the tool's definition Tool name 'get_batch_results' and description 'Get results for all completed and failed tasks in a batch' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_batch_results gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hive, and nothing reaches the server without passing your rules. This is the rule we recommend for get_batch_results:
{
"version": "1",
"default": "deny",
"tools": {
"get_batch_results": {}
}
}get_batch_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get results for all completed and failed tasks in a batch. It is categorised as a Read tool in the Hive MCP Server, which means it retrieves data without modifying state.
Register the Hive MCP server in PolicyLayer and add a rule for get_batch_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 Hive. Nothing to install.
get_batch_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_batch_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_batch_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_batch_results is provided by the Hive MCP server (saikodi/hive-compute-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hive, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Hive tools catalogued and risk-classified — across an index of 43,000+ MCP servers.