AI agents call get_etsi_document 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 performs document lookup and retrieval (search follow-up operation) from a technical specification catalog. The action is a simple read operation to inspect metadata and versions of ETSI documents. It has no side effects, cannot modify data, and presents minimal risk if misused by an AI agent. The blast radius is limited to information disclosure of publicly available specifications.
From the tool's definition Tool retrieves document metadata and file information from ETSI catalog. Terms 'Get' and 'inspect' indicate data retrieval operations with no modification capability. No destructive, financial, or code execution elements present.
Attacks that exploit this kind of access
Get one ETSI catalog document with version and optional file metadata. Use after search_etsi_catalog to inspect latest and historical versions. 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 get_etsi_document: 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.
get_etsi_document 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_etsi_document 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_etsi_document. 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_etsi_document 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 →