AI agents use add_new_resource to create or update resources in Neptune MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neptune MCP Server environment.
With empty description, we rely on the tool name and server context. 'add_new_resource' most naturally means creating or modifying a resource (infrastructure component) in AWS, which is reversible (can be deleted or updated later). This is a Write operation rather than Execute because it doesn't run arbitrary code—it adds a defined resource type to infrastructure.
From the tool's definition Tool name 'add_new_resource' combined with server context of AWS deployment and Infrastructure as Code. The sibling tools include 'deploy_project' and 'delete_project', indicating this server manages cloud infrastructure lifecycle.
Documented attack patterns abuse exactly the kind of access add_new_resource 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 add_new_resource:
{
"version": "1",
"default": "deny",
"tools": {
"add_new_resource": {
"limits": [
{
"counter": "add_new_resource_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_new_resource stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_new_resource. It is categorised as a Write tool in the Neptune MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neptune MCP Server MCP server in PolicyLayer and add a rule for add_new_resource: 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.
add_new_resource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_new_resource 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 add_new_resource. 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.
add_new_resource 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.