AI agents call reconcile_cross_saas to retrieve information from Cockpit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Reconciliation in this context is a read/detection operation: it compares records and identifies duplicates but does not explicitly create, modify, or delete data. The medium severity reflects the sensitive financial accounting context — misuse or misconfiguration could surface incorrect reconciliation results affecting tax filings — but the operation itself is non-destructive.
From the tool's definition 'Detects duplicate fingerprints within freee' — the tool performs detection/comparison across data sources without indicating it modifies or deletes any records. 'Currently freee-only mode' and 'MF connector pending' suggest a read/analysis operation.
Attacks that exploit this kind of access
Cross-SaaS reconciliation (= freee ↔ MF). Currently freee-only mode (= MF connector pending Phase 1.B). Detects duplicate fingerprints within freee. It is categorised as a Read tool in the Cockpit MCP Server, which means it retrieves data without modifying state.
Register the Cockpit MCP server in PolicyLayer and add a rule for reconcile_cross_saas: 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 Cockpit. Nothing to install.
reconcile_cross_saas 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 reconcile_cross_saas 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 reconcile_cross_saas. 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.
reconcile_cross_saas is provided by the Cockpit MCP server (michielinksee/kansei-link-cockpit). 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 →