AI agents use db.save_finding to create or update resources in VulneraMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VulneraMCP environment.
The name suggests this tool writes a new finding record to the PostgreSQL database. 'Save' is a classic write operation (create/update). No description is provided, which lowers confidence, but given the context of a bug bounty platform with PostgreSQL storage and sibling tools like db.get_findings, db.get_statistics, this is almost certainly a write operation storing vulnerability findings.
From the tool's definition Tool name 'db.save_finding' — 'save' implies creating or storing a new record in the database.
Documented attack patterns abuse exactly the kind of access db.save_finding gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VulneraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for db.save_finding:
{
"version": "1",
"default": "deny",
"tools": {
"db.save_finding": {
"limits": [
{
"counter": "db.save_finding_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}db.save_finding 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.
db.save_finding. It is categorised as a Write tool in the VulneraMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vulnera MCP server in PolicyLayer and add a rule for db.save_finding: 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 VulneraMCP. Nothing to install.
db.save_finding 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 db.save_finding 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 db.save_finding. 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.
db.save_finding is provided by the Vulnera MCP server (telmon95/vulneramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 VulneraMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 VulneraMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.