AI agents call get_cosmos to retrieve information from Astrolabe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_cosmos' and context of a documentation search/retrieval server strongly indicate a read-only data retrieval function. The pattern of sibling tools (get_*, read_*, list_*, search_*) supports classification as a Read operation with no side effects.
From the tool's definition Tool name 'get_cosmos' and sibling tools including 'get_card', 'read_doc', 'list_docs', 'search_docs', 'deep_search' suggest retrieval operations.
Attacks that exploit this kind of access
get_cosmos. It is categorised as a Read tool in the Astrolabe MCP Server, which means it retrieves data without modifying state.
Register the Astrolabe MCP server in PolicyLayer and add a rule for get_cosmos: 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 Astrolabe. Nothing to install.
get_cosmos 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_cosmos 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_cosmos. 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_cosmos is provided by the Astrolabe MCP server (zebrr/astrolabe-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 →