Get the catalog of all supported 3GPP specifications with metadata. Returns spec IDs, titles, versions, descriptions, section counts, and page totals. Use this first to discover available specs before drilling into TOC or sections.
AI agents call get_spec_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 metadata about 3GPP specifications without any side effects. It enables discovery of available specifications but does not modify, execute, or delete any data. It is a straightforward Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description explicitly states it 'Get[s] the catalog' and 'Returns spec IDs, titles, versions, descriptions, section counts, and page totals' — purely retrieval operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get the catalog of all supported 3GPP specifications with metadata. Returns spec IDs, titles, versions, descriptions, section counts, and page totals. Use this first to discover available specs before drilling into TOC or sections. 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_spec_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.
get_spec_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 get_spec_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 get_spec_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.
get_spec_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 →