[Phase 3 - Not yet implemented] Run error check and get review results before filing.
AI agents invoke review_return to trigger actions in FreeTaxUSA MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes validation/review logic as part of a tax filing system. Although review itself is not destructive, it falls under Execute because it runs computational checks and interacts with an external tax system. The high severity reflects that misuse (e.g., reviewing a fraudulent return, or bypassing safeguards) could facilitate financial harm and tax filing violations.
From the tool's definition The tool is explicitly described as running an 'error check' before filing, which involves executing validation logic on tax return data.
Attacks that exploit this kind of access
[Phase 3 - Not yet implemented] Run error check and get review results before filing. It is categorised as a Execute tool in the FreeTaxUSA MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FreeTaxUSA MCP Server MCP server in PolicyLayer and add a rule for review_return: 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 FreeTaxUSA MCP Server. Nothing to install.
review_return is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the review_return 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 review_return. 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.
review_return is provided by the FreeTaxUSA MCP Server MCP server (schwarztim/freetaxusa-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 →