This record as markdown: /tools/io-github-portel-dev-ncp/get-info.md
What get_info does on Ncp
AI agents call get_info to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_info is rated Low
The tool retrieves information from an external API (New Relic) without creating, modifying, deleting, or executing any operations. This is a straightforward read-only query operation. Severity is low because information retrieval typically has minimal risk unless the data itself is highly sensitive, but the tool itself poses no destructive or operational risk.
From the tool's definition Tool name 'get_info' and description 'Get information from newrelic-api' indicate a data retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_info, this is the rule to start with:
get_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every get_info call is checked against it from then on.
Questions about get_info
Get information from newrelic-api. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for get_info: 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 Ncp. Nothing to install.
get_info 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_info 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_info. 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_info is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue