Returns step-by-step operational instructions for expanding the 3GPP/RFC corpus. Use this tool when: - A document is missing from the corpus and needs to be downloaded and ingested - You want to catalog ETSI metadata before downloading documents - You need to know the ETSI URL pattern for a speci...
AI agents call get_ingest_guide 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 provides informational guidance about document ingestion procedures. It does not execute ingestion operations, create/modify data in the corpus, or trigger external downloads/pipeline runs—it only returns instructional information. The most severe use case ('run the AutoRAG pipeline') is conditional and appears to be guidance rather than direct execution by the tool itself.
From the tool's definition Tool returns 'step-by-step operational instructions' and is used to 'catalog ETSI metadata' and 'know the ETSI URL pattern'.
Attacks that exploit this kind of access
Returns step-by-step operational instructions for expanding the 3GPP/RFC corpus. Use this tool when: - A document is missing from the corpus and needs to be downloaded and ingested - You want to catalog ETSI metadata before downloading documents - You need to know the ETSI URL pattern for a specific spec - You want to run the AutoRAG pipeline after downloading new PDFs - You need to add RFC documents (SIP, Diameter, TLS, OAuth, QUIC, etc.) to the corpus Four guides available: -. 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_ingest_guide: 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_ingest_guide 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_ingest_guide 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_ingest_guide. 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_ingest_guide 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 →