Check whether a PlugLayer slug is available inside a project before deploying or renaming an app/database.
AI agents call check_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 slug identifier without creating, modifying, or deleting any resources. It is purely informational and used for pre-flight validation before other operations. No state is changed, and there is no risk of data loss, code execution, or financial impact.
From the tool's definition Tool description states 'Check whether a PlugLayer slug is available' — a query operation with no side effects. The verb 'check' indicates a read-only validation before deployment.
Attacks that exploit this kind of access
Check whether a PlugLayer slug is available inside a project before deploying or renaming an app/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_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_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_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_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_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 →