List all astronauts currently in space and which craft they are on.
AI agents call get_people_in_space to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves public information about astronauts in space. It performs a read-only operation with no capability to modify, delete, execute, or commit financial transactions. The data retrieved is typically public information from space agencies. The blast radius of misuse is minimal—worst case being information disclosure of already-public data.
From the tool's definition Tool name 'get_people_in_space' and description 'List all astronauts currently in space' indicate a retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
List all astronauts currently in space and which craft they are on. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for get_people_in_space: 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 Integrations MCP. Nothing to install.
get_people_in_space 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_people_in_space 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_people_in_space. 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_people_in_space is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →