actual_session_close
Close an idle MCP session to free up connection slots. Useful when you get
This record as markdown: /tools/actual/actual-session-close.md
What actual_session_close does on Actual
AI agents call actual_session_close as a supporting operation in Actual workflows.
Why actual_session_close is rated Low
This tool closes an MCP session (a connection/resource handle), not financial data or user content. It is a session/resource management operation — it doesn't read, write, execute, or delete user data, nor does it involve financial transactions. It is closest to 'Other' as it manages infrastructure/connection state rather than application data.
From the tool's definition Close an idle MCP session to free up connection slots
Attacks that exploit this kind of access
The rule that runs actual_session_close safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Actual, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For actual_session_close, this is the rule to start with:
actual_session_close gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_session_close call is checked against it from then on.
Questions about actual_session_close
Close an idle MCP session to free up connection slots. Useful when you get. It is categorised as a Other tool in the Actual MCP Server, which means it performs auxiliary operations.
Register the Actual MCP server in PolicyLayer and add a rule for actual_session_close: 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 Actual. Nothing to install.
actual_session_close is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the actual_session_close 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 actual_session_close. 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.
actual_session_close is provided by the Actual MCP server (actual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Actual, and thousands of servers like it.
This server
Across the catalogue