AI agents call search_etsi_catalog to retrieve information from 3gpp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries catalog metadata about ETSI documents without creating, modifying, deleting, or executing any operations. It is a straightforward information retrieval function that poses minimal security risk, as it only exposes metadata about document catalogs rather than sensitive content or operational capabilities.
From the tool's definition Tool description states it 'searches cataloged documents and versions' and 'searches the ETSI delivery catalog metadata.' The verb 'search' combined with 'metadata' and 'catalog' indicates read-only retrieval of information with no modification or side…
Attacks that exploit this kind of access
Search the ETSI delivery catalog metadata. This searches cataloged documents and versions, including documents that have not been downloaded or embedded yet. It is categorised as a Read tool in the 3gpp MCP Server, which means it retrieves data without modifying state.
Register the 3gpp MCP server in PolicyLayer and add a rule for search_etsi_catalog: 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 3gpp. Nothing to install.
search_etsi_catalog 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_etsi_catalog 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_etsi_catalog. 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_etsi_catalog is provided by the 3gpp MCP server (lee-sihyeon/mcp-server-3gpp). 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 →