Buscar lugares (bancos, oficinas SAT, etc.) usando Google Places via EXPO_PUBLIC_GOOGLE_MAPS_API_KEY.
AI agents call search_places_tool to retrieve information from estudIA-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves geographical location data (banks, tax offices, etc.) from Google Places. It performs a semantic or location-based query and returns results without modifying, deleting, or executing any operations. The use of an API key is for authentication to access the public Google Places service, not for enabling destructive or financial operations.
From the tool's definition Tool description explicitly states 'Buscar lugares' (search places) using Google Places API. The verb 'search' and the context of querying a locations database indicates read-only retrieval with no side effects.
Attacks that exploit this kind of access
Buscar lugares (bancos, oficinas SAT, etc.) usando Google Places via EXPO_PUBLIC_GOOGLE_MAPS_API_KEY. It is categorised as a Read tool in the estudIA-MCP MCP Server, which means it retrieves data without modifying state.
Register the estudIA- MCP server in PolicyLayer and add a rule for search_places_tool: 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 estudIA-MCP. Nothing to install.
search_places_tool 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_places_tool 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_places_tool. 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_places_tool is provided by the estudIA- MCP server (jpaboytes/estudia-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 →