Check whether a database/Data Layer slug is available in a project before provisioning or renaming a database.
AI agents call check_database_slug_availability to retrieve information from PlugLayer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves availability status of a database slug—a pure read operation with no side effects. It does not create, modify, delete, or execute operations; it only queries existing state to determine if a slug can be provisioned.
From the tool's definition Tool name 'check_database_slug_availability' and description 'Check whether a database/Data Layer slug is available' indicate a query operation that performs availability verification without modifying state.
Attacks that exploit this kind of access
Check whether a database/Data Layer slug is available in a project before provisioning or renaming a database. It is categorised as a Read tool in the PlugLayer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for check_database_slug_availability: 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 PlugLayer MCP Server. Nothing to install.
check_database_slug_availability 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 check_database_slug_availability 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 check_database_slug_availability. 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.
check_database_slug_availability is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →