Search planets Star Wars, in API by name
AI agents call search_planets to retrieve information from Simple MCP Server - Star Wars API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation against the SWAPI API to retrieve planet data by name. It retrieves information from a public API with no ability to modify, delete, or execute arbitrary operations. The blast radius of misuse is minimal—an agent could only retrieve data that is publicly available. This is a straightforward Read category tool.
From the tool's definition Tool name 'search_planets' and description 'Search planets Star Wars, in API by name' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Search planets Star Wars, in API by name. It is categorised as a Read tool in the Simple MCP Server - Star Wars API MCP Server, which means it retrieves data without modifying state.
Register the Simple MCP Server - Star Wars API MCP server in PolicyLayer and add a rule for search_planets: 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 Simple MCP Server - Star Wars API. Nothing to install.
search_planets 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 search_planets 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 search_planets. 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.
search_planets is provided by the Simple MCP Server - Star Wars API MCP server (ramosjsouza/simple_mcp_server). 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 →