Medium Risk

plan_cross_border

THE cross-border tool. Use this — not compare_jurisdictions — whenever a person's facts touch more than one country: a US citizen living abroad, a dual resident, someone changing residence, a non-dom, an expatriating citizen, or an owner of a foreign trust/company. Unlike compare_jurisdictions (w...

Part of the OpenAccountants server.

plan_cross_border can modify OpenAccountants data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE OPENACCOUNTANTS →

Free to start. No card required.

AI agents use plan_cross_border to create or modify resources in OpenAccountants. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call plan_cross_border repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach OpenAccountants.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "plan_cross_border": {
      "limits": [
        {
          "counter": "plan_cross_border_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full OpenAccountants policy for all 13 tools.

Get this rule live on your own OpenAccountants server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENACCOUNTANTS →

View all 13 tools →

These attack patterns abuse exactly the kind of access plan_cross_border gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so plan_cross_border only ever does what you allow.

SECURE OPENACCOUNTANTS →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the plan_cross_border tool do? +

THE cross-border tool. Use this — not compare_jurisdictions — whenever a person's facts touch more than one country: a US citizen living abroad, a dual resident, someone changing residence, a non-dom, an expatriating citizen, or an owner of a foreign trust/company. Unlike compare_jurisdictions (which loads each country as an independent block and disclaims treaty/PE interaction), this returns a SEQUENCED plan: it builds the residency/citizenship/domicile map, identifies the country skills AND the international topic skills (FEIE/FTC, FBAR/FATCA, CFC/GILTI, foreign trusts, exit tax) the facts engage, fixes the ORDER of events (order changes the tax — e.g. sever residency before vs. after a sale), names the verifier per country, states the treaty bridge for double-tax relief, and mandates a request_accountant_review hand-off to the lead country's accountant. Always load cross-border-tax-router + cross-border-tax-workflow-base first (returned in load_first). Output is research-grade (tier 2) until a licensed human signs off.. It is categorised as a Write tool in the OpenAccountants MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on plan_cross_border? +

Register the OpenAccountants MCP server in PolicyLayer and add a rule for plan_cross_border: 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 OpenAccountants. Nothing to install.

What risk level is plan_cross_border? +

plan_cross_border is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit plan_cross_border? +

Yes. Add a rate_limit block to the plan_cross_border 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.

How do I block plan_cross_border completely? +

Set action: deny in the PolicyLayer policy for plan_cross_border. 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.

What MCP server provides plan_cross_border? +

plan_cross_border is provided by the OpenAccountants MCP server (pypi:openaccountants-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenAccountants tool call.

Deterministic rules across all 13 OpenAccountants tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.