AI agents call info to retrieve information from Neptune MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without an explicit description, the name 'info' most likely retrieves or queries information about a resource or deployment. No evidence suggests mutation, deletion, execution of external code, or financial impact. The low confidence reflects the empty description—if this tool actually executes commands or modifies state, the classification should be reconsidered with clarification.
From the tool's definition Tool name 'info' with empty description suggests a retrieval or informational operation typical of Read-category tools (e.g., get, fetch).
Documented attack patterns abuse exactly the kind of access info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Neptune MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for info:
{
"version": "1",
"default": "deny",
"tools": {
"info": {}
}
}info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
info. It is categorised as a Read tool in the Neptune MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neptune MCP Server MCP server in PolicyLayer and add a rule for 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 Neptune MCP Server. Nothing to install.
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 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 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.
info is provided by the Neptune MCP Server MCP server (shuttle-hq/neptune-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Neptune MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Neptune MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.