db_add_database
AI agents use db_add_database to create or update resources in Custom MCP Database Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Custom MCP Database Server environment.
The tool modifies the middleware's stored database configuration by adding a new database connection without irreversibly destroying data. This qualifies as Write (creates/registers data reversibly) rather than Execute (which would require runtime code execution). Severity is medium because misconfiguration could grant unintended database access, but the action itself is reversible by removing the alias.
From the tool's definition Tool name 'db_add_database' indicates a data modification operation that creates or registers a new database connection/alias in the middleware control plane.
Attacks that exploit this kind of access
db_add_database. It is categorised as a Write tool in the Custom MCP Database Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Custom MCP Database Server MCP server in PolicyLayer and add a rule for db_add_database: 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 Custom MCP Database Server. Nothing to install.
db_add_database 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_add_database 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_add_database. 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_add_database is provided by the Custom MCP Database Server MCP server (renanlido/custom-mcp-database). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
db_add_database is one line of Custom MCP Database Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →