AI agents call get_events_schema to retrieve information from DPSCoach without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns schema information without modifying, executing queries, deleting data, or performing any side effects. It is purely informational—allowing users to understand the structure of available data. While schema exposure could theoretically inform an attacker about database internals, in this context it is a read-only introspection tool with minimal blast radius.
From the tool's definition Tool name 'get_events_schema' and description 'Return the DuckDB events schema' indicate a retrieval operation that exposes metadata about the database structure for informational purposes only.
Attacks that exploit this kind of access
Return the DuckDB events schema exposed for ad-hoc queries. It is categorised as a Read tool in the DPSCoach MCP Server, which means it retrieves data without modifying state.
Register the DPSCoach MCP server in PolicyLayer and add a rule for get_events_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 DPSCoach. Nothing to install.
get_events_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 get_events_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 get_events_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.
get_events_schema is provided by the DPSCoach MCP server (stalcup-dev/tl-dps-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 →