Obtiene un esquema guardado. Si snapshot_id es None, devuelve el más reciente
AI agents call db_schema_get to retrieve information from Schema Engram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation that queries previously saved database schema snapshots. It has no side effects—it only reads data from the local SQLite persistent memory store. Even though it operates on a database, the action itself is a read operation (get/fetch). The sibling tools db_schema_delete and db_schema_update handle write and destructive operations, but this tool is purely read-only.
From the tool's definition Tool name is 'db_schema_get' and description states 'Obtiene un esquema guardado' (Retrieves a saved schema). The operation retrieves or queries stored schema data without modifying or deleting anything.
Attacks that exploit this kind of access
Obtiene un esquema guardado. Si snapshot_id es None, devuelve el más reciente. It is categorised as a Read tool in the Schema Engram MCP Server, which means it retrieves data without modifying state.
Register the Schema Engram MCP server in PolicyLayer and add a rule for db_schema_get: 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 Schema Engram. Nothing to install.
db_schema_get 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 db_schema_get 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_schema_get. 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_schema_get is provided by the Schema Engram MCP server (wabox32/schema-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 →