AI agents call get_emm_cause 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 static reference information about standardized cause codes from 3GPP specifications. It performs a lookup/get operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an AI could only retrieve unwanted documentation, not affect systems. This is a straightforward Read category tool.
From the tool's definition Tool description indicates 'Get detailed information' about EMM/5GMM cause values, a retrieval operation. The server's overall purpose is to 'search and retrieve information from 3GPP specification documents' with 'pre-processed data'.
Attacks that exploit this kind of access
Get detailed information about EMM cause (LTE) or 5GMM cause (5G) values. 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_emm_cause: 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_emm_cause 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_emm_cause 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_emm_cause. 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_emm_cause 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 →