Returns all tables/collections in the connected database with column names, types,
AI agents call dlp_get_schema to retrieve information from Database Lookup Protocol (DLP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about database structure (schema information) without creating, modifying, or deleting any data. It is a passive inspection capability designed to help AI understand schema for code generation.
From the tool's definition Tool name 'dlp_get_schema' and description state it 'Returns all tables/collections in the connected database with column names, types' — a pure retrieval operation with no modifications.
Documented attack patterns abuse exactly the kind of access dlp_get_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Database Lookup Protocol (DLP), and nothing reaches the server without passing your rules. This is the rule we recommend for dlp_get_schema:
{
"version": "1",
"default": "deny",
"tools": {
"dlp_get_schema": {}
}
}dlp_get_schema is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns all tables/collections in the connected database with column names, types,. It is categorised as a Read tool in the Database Lookup Protocol (DLP) MCP Server, which means it retrieves data without modifying state.
Register the Database Lookup Protocol (DLP) MCP server in PolicyLayer and add a rule for dlp_get_schema: 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 Database Lookup Protocol (DLP). Nothing to install.
dlp_get_schema 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 dlp_get_schema 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 dlp_get_schema. 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.
dlp_get_schema is provided by the Database Lookup Protocol (DLP) MCP server (kalyangupta12/database-lookup-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Database Lookup Protocol (DLP), 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.
3 Database Lookup Protocol (DLP) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.