Set the filing status (single, married_joint, married_separate, head_of_household, qualifying_widow).
AI agents use fill_filing_status to create or update resources in FreeTaxUSA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FreeTaxUSA MCP Server environment.
The tool creates or modifies tax filing data (a core component of a tax return) through browser automation. While it doesn't delete data (not Destructive) or move money directly (not Financial), it reversibly writes/updates form state.
From the tool's definition Tool name 'fill_filing_status' and description indicating it 'Set[s] the filing status' to one of several enumerated options. This modifies tax form data within the FreeTaxUSA system.
Attacks that exploit this kind of access
Set the filing status (single, married_joint, married_separate, head_of_household, qualifying_widow). It is categorised as a Write tool in the FreeTaxUSA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FreeTaxUSA MCP Server MCP server in PolicyLayer and add a rule for fill_filing_status: 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.
fill_filing_status 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 fill_filing_status 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 fill_filing_status. 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.
fill_filing_status 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 →