Retrieve cross-spec reference relationships for a given spec. Returns: - outgoing: specs that THIS spec references (cites) - incoming: specs that reference THIS spec (cited-by) Use to navigate the dependency graph between 3GPP specs and RFCs.
AI agents call get_spec_references 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 a purely informational lookup—it queries and returns metadata about specification references (incoming and outgoing citations) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal; an agent cannot damage systems or data through reference lookups. Classification as Read is appropriate for a search/retrieval operation with no side effects.
From the tool's definition Tool retrieves cross-spec reference relationships and navigates dependency graphs between specifications. Uses action words 'Retrieve' and 'navigate' indicating passive information lookup with no modification or execution capability.
Attacks that exploit this kind of access
Retrieve cross-spec reference relationships for a given spec. Returns: - outgoing: specs that THIS spec references (cites) - incoming: specs that reference THIS spec (cited-by) Use to navigate the dependency graph between 3GPP specs and RFCs. 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_references: 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_references 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_references 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_references. 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_references 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 →