Statistical profile and quality check of a cached dataset.
AI agents call profile_data to retrieve information from Ontario Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
profile_data retrieves and analyzes statistical properties of an existing dataset. It has no side effects—it does not create, modify, delete, or execute code. This is a classic Read operation: data retrieval and analysis with no risk of data loss or external execution. Severity is low because misuse would only expose data that is already accessible in the cache, with no ability to modify systems or data.
From the tool's definition Tool performs 'statistical profile and quality check' which are analysis operations that query and examine data without modifying, deleting, or executing external commands. The description indicates read-only introspection of cached datasets.
Attacks that exploit this kind of access
Statistical profile and quality check of a cached dataset. It is categorised as a Read tool in the Ontario Data MCP Server, which means it retrieves data without modifying state.
Register the Ontario Data MCP server in PolicyLayer and add a rule for profile_data: 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 Ontario Data. Nothing to install.
profile_data 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 profile_data 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 profile_data. 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.
profile_data is provided by the Ontario Data MCP server (sprine/ontario-data-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 →