search_companies_by_name_and_city
AI agents call search_companies_by_name_and_city to retrieve information from MCP NIF PT without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves company information from a public API based on search criteria (name and city). It performs a query operation with no side effects—no data is created, modified, or deleted. The empty description slightly reduces confidence, but the naming convention and server context clearly indicate a read-only search function.
From the tool's definition Tool name 'search_companies_by_name_and_city' indicates a search operation. Server description states it 'Supports searching by NIF, company name or city' and 'Enables querying and analyzing information'.
Attacks that exploit this kind of access
search_companies_by_name_and_city. It is categorised as a Read tool in the MCP NIF PT MCP Server, which means it retrieves data without modifying state.
Register the MCP NIF PT MCP server in PolicyLayer and add a rule for search_companies_by_name_and_city: 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 MCP NIF PT. Nothing to install.
search_companies_by_name_and_city 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_companies_by_name_and_city 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_companies_by_name_and_city. 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_companies_by_name_and_city is provided by the MCP NIF PT MCP server (ruicarvalho1/mcp_nif). 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 →