Return a list of conversions between two dates (YYYY-MM-DD)
AI agents call get_conversions to retrieve information from RedTrack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical conversion data within a date range. It is a read-only query with no capability to modify, delete, execute code, or trigger financial transactions. The blast radius of misuse is minimal — an attacker could only access existing conversion records, not alter them or cause irreversible harm.
From the tool's definition Tool name is 'get_conversions' and description states 'Return a list of conversions between two dates' — a query operation that retrieves data with no modification or side effects.
Attacks that exploit this kind of access
Return a list of conversions between two dates (YYYY-MM-DD). It is categorised as a Read tool in the RedTrack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RedTrack MCP Server MCP server in PolicyLayer and add a rule for get_conversions: 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 RedTrack MCP Server. Nothing to install.
get_conversions 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_conversions 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_conversions. 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_conversions is provided by the RedTrack MCP Server MCP server (oldsnakenewtrik/redtrack_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 →