Scan a table for unusual patterns: volume drops/spikes, data gaps, value concentration, high null rates, stale data. Severity-ranked alerts. Tables > 100k rows use a sampled path (~5%). Dialect-aware sampling.
AI agents call detect_anomalies to retrieve information from ThinAir Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
detect_anomalies is a purely analytical tool that queries and examines existing table data to identify anomalies. It retrieves information, applies statistical or pattern-matching logic, and reports findings without modifying, executing external commands, or deleting data. This is a classic Read operation.
From the tool's definition Tool performs scanning and analysis of table data to detect patterns—'Scan a table for unusual patterns: volume drops/spikes, data gaps, value concentration, high null rates, stale data.' No data modification, deletion, or command execution is mentioned.
Attacks that exploit this kind of access
Scan a table for unusual patterns: volume drops/spikes, data gaps, value concentration, high null rates, stale data. Severity-ranked alerts. Tables > 100k rows use a sampled path (~5%). Dialect-aware sampling. It is categorised as a Read tool in the ThinAir Data MCP Server, which means it retrieves data without modifying state.
Register the ThinAir Data MCP server in PolicyLayer and add a rule for detect_anomalies: 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 ThinAir Data. Nothing to install.
detect_anomalies 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 detect_anomalies 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 detect_anomalies. 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.
detect_anomalies is provided by the ThinAir Data MCP server (thinairtelematics/thinair-data). 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 →