Fetch a Passpoint identity / ANQP NAI realm profile by name.
AI agents call get_passpoint_identity_profile to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data (a Passpoint identity profile) by querying an existing resource. The verb 'fetch' and the action of retrieving profile information by name are characteristic of Read operations. There is no indication of data modification, deletion, code execution, or financial operations. The blast radius if misused is minimal — an agent could only access existing profile information.
From the tool's definition Tool description explicitly states 'Fetch a Passpoint identity / ANQP NAI realm profile by name' — fetch is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch a Passpoint identity / ANQP NAI realm profile by name. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for get_passpoint_identity_profile: 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 API-Central. Nothing to install.
get_passpoint_identity_profile 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_passpoint_identity_profile 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_passpoint_identity_profile. 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_passpoint_identity_profile is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →