AI agents use apply_export_profile to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates or modifies data (the exported data bundle) in a reversible manner by applying profile-based transformations. While it involves security-sensitive operations (encryption, redaction), it is not destructive (data remains intact), not financial, and not truly Execute-level (it applies a pre-defined profile rather than running arbitrary code).
From the tool's definition The tool description states it 'Apply[s] secure export profile... to data bundle', indicating it modifies or transforms a data bundle by applying an export profile configuration.
Attacks that exploit this kind of access
Apply secure export profile (redacted, encrypted, plaintext) to data bundle. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for apply_export_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 Todos. Nothing to install.
apply_export_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_export_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 apply_export_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.
apply_export_profile is provided by the Todos MCP server (@hasna/todos). 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 →