Buscar guías por su nombre.
AI agents call get_leader_by_name to retrieve information from LumbreTravel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves leader (guide) data by name parameter. It performs a lookup operation with no side effects, fitting the Read category. The blast radius is minimal—an AI agent misusing this would only retrieve existing guide information, which poses no significant risk. Severity is low as this is a basic read operation on travel guide records.
From the tool's definition Tool name 'get_leader_by_name' and description 'Buscar guías por su nombre' (Search guides by their name) indicate a retrieval operation. No modification, deletion, or execution is implied.
Attacks that exploit this kind of access
Buscar guías por su nombre. It is categorised as a Read tool in the LumbreTravel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LumbreTravel MCP Server MCP server in PolicyLayer and add a rule for get_leader_by_name: 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 LumbreTravel MCP Server. Nothing to install.
get_leader_by_name 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_leader_by_name 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_leader_by_name. 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_leader_by_name is provided by the LumbreTravel MCP Server MCP server (lumile/lumbretravel-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 →