buscar_por_nombre
AI agents call buscar_por_nombre to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name and context strongly suggest this tool retrieves data by name without side effects. The empty description reduces confidence slightly, but the naming convention (search operation) and sibling tools (check_overbudget, compare_budget, get_estado_completo, registrar_solicitud) all indicate read-only query operations on budget data. No evidence of modification, deletion, code execution, or financial movement.
From the tool's definition Tool name 'buscar_por_nombre' translates to 'search by name', suggesting a query operation. The tool is part of a MySQL server for 'querying departmental budget information'. No destructive, financial, or execution capabilities are indicated.
Attacks that exploit this kind of access
buscar_por_nombre. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for buscar_por_nombre: 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 MySQL MCP Server. Nothing to install.
buscar_por_nombre 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 buscar_por_nombre 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 buscar_por_nombre. 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.
buscar_por_nombre is provided by the MySQL MCP Server MCP server (w2pwinlinux/mcp-server-presupuesto-mysql1). 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 →