FULL data quality + compliance report for a table: per-column stats PLUS a 0-100 health score, type-gated PII detection (email / phone / SSN / etc.), and insight warnings. Use this when the user says
AI agents call data_profile 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.
This is fundamentally a Read operation—it queries table metadata and performs analysis to produce a report. However, severity is elevated to 'medium' rather than 'low' because PII detection reveals sensitive personal information (SSN, phone, email) that could be exposed if an agent misuses this tool. The tool itself doesn't modify data, but the sensitive nature of the information it surfaces justifies elevated risk.
From the tool's definition Tool generates reports with column statistics, health scores, PII detection (email/phone/SSN), and insights without modifying data. Description says 'FULL data quality + compliance report' indicating data retrieval and analysis.
Attacks that exploit this kind of access
FULL data quality + compliance report for a table: per-column stats PLUS a 0-100 health score, type-gated PII detection (email / phone / SSN / etc.), and insight warnings. Use this when the user says. 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 data_profile: 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.
data_profile 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 data_profile 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 data_profile. 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.
data_profile 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 →