Diagnose the freee connection in ONE shot. Checks: (1) where the access token is sourced (FREEE_ACCESS_TOKEN env vs secrets file), (2) whether the token is expired (24h TTL, no auto-refresh), (3) lists ALL 事業所 the token can access and flags whether your configured company_id is live — fixes the
AI agents call freee_doctor 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.
freee_doctor is a diagnostic utility that retrieves and reports on authentication state, token validity, and accessible company entities. It performs no data mutations, no external command execution, and no irreversible actions. The tool queries system state to help troubleshoot connectivity issues, making it a pure Read operation with minimal blast radius if misused.
From the tool's definition Tool performs diagnostic checks: 'Checks: (1) where the access token is sourced', '(2) whether the token is expired', '(3) lists ALL 事業所 the token can access'.
Attacks that exploit this kind of access
Diagnose the freee connection in ONE shot. Checks: (1) where the access token is sourced (FREEE_ACCESS_TOKEN env vs secrets file), (2) whether the token is expired (24h TTL, no auto-refresh), (3) lists ALL 事業所 the token can access and flags whether your configured company_id is live — fixes the. 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 freee_doctor: 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.
freee_doctor 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 freee_doctor 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 freee_doctor. 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.
freee_doctor 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 →