custom_name
AI agents call custom_name 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.
Given the empty description, classification relies on context: the MCP NIF.PT server is explicitly described as enabling 'querying and analyzing information' about Portuguese companies. All named sibling tools are read-only queries (search, get, is_*). Without evidence that 'custom_name' performs writes, deletes, or executes arbitrary operations, the safest assumption is that it retrieves data.
From the tool's definition Tool named 'custom_name' with empty description on MCP NIF.PT server. Based on sibling tools (find_nif_by_name, get_company, is_accounting_company, is_active, search_companies_by_name_and_city), the server is designed for querying Portuguese company data…
Attacks that exploit this kind of access
custom_name. 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 custom_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 MCP NIF PT. Nothing to install.
custom_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 custom_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 custom_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.
custom_name 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 →