Get pricing, tier details, and setup instructions for the NDI MCP Server.
AI agents call get_access to retrieve information from NDI-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static information about pricing tiers and setup instructions. It is a read-only operation with no side effects, no code execution, no data modification, and no financial impact. The low severity reflects minimal blast radius if misused—an AI agent would only retrieve publicly available or semi-public access information.
From the tool's definition Tool name 'get_access' and description 'Get pricing, tier details, and setup instructions' indicates retrieval of informational content about service access, pricing, and setup documentation.
Attacks that exploit this kind of access
Get pricing, tier details, and setup instructions for the NDI MCP Server. It is categorised as a Read tool in the NDI-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the NDI-MCP-Server MCP server in PolicyLayer and add a rule for get_access: 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 NDI-MCP-Server. Nothing to install.
get_access 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_access 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_access. 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_access is provided by the NDI-MCP-Server MCP server (CREIntel/ndi-mcp-server). 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 →