AI agents call list_projects 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.
A 'list' operation by convention retrieves and returns data without side effects. The absence of a description lowers confidence slightly, but the naming pattern and context of sibling read-only tools strongly indicate this is a query that enumerates projects rather than creating, modifying, or deleting them. No destructive, financial, or execution risk is evident.
From the tool's definition Tool named 'list_projects' with no description provided; naming convention suggests a query operation that retrieves a list of existing projects without modification.
Documented attack patterns abuse exactly the kind of access list_projects 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 list_projects:
{
"version": "1",
"default": "deny",
"tools": {
"list_projects": {}
}
}list_projects 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.
list_projects. 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 list_projects: 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.
list_projects 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 list_projects 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 list_projects. 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.
list_projects 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.