AI agents call get_gravity_task_status to retrieve information from Macrocosmos MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an existing background task (Gravity task) and returns status information. It is a read-only operation that retrieves data about task progress or state. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal — an agent could only inspect task statuses, not affect them or trigger unintended operations.
From the tool's definition Tool name contains 'get' and description states 'Get the status' — both indicate a retrieval operation with no side effects. Returns task status information without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access get_gravity_task_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Macrocosmos MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_gravity_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_gravity_task_status": {}
}
}get_gravity_task_status 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 the status of a Gravity task. It is categorised as a Read tool in the Macrocosmos MCP MCP Server, which means it retrieves data without modifying state.
Register the Macrocosmos MCP server in PolicyLayer and add a rule for get_gravity_task_status: 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 Macrocosmos MCP. Nothing to install.
get_gravity_task_status 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_gravity_task_status 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_gravity_task_status. 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_gravity_task_status is provided by the Macrocosmos MCP server (macrocosm-os/macrocosmos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Macrocosmos MCP, 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.
6 Macrocosmos MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.