actual_server_info
Get MCP server version and system information. Returns: - Server version - Server name - Node.js version - MCP SDK version - Actual Budget API version - Total tools available - Uptime Use this to check server status, verify version compatibility, or debug issues.
This record as markdown: /tools/actual/actual-server-info.md
What actual_server_info does on Actual
AI agents call actual_server_info to retrieve information from Actual without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why actual_server_info is rated Low
This tool only retrieves and returns metadata about the server state and environment. There is no modification, deletion, execution of arbitrary code, or financial impact. It is purely informational and read-only, making it the lowest risk category.
From the tool's definition Tool description states 'Get MCP server version and system information' and explicitly lists returned values as server version, name, Node.js version, MCP SDK version, Actual Budget API version, total tools available, and uptime.
Attacks that exploit this kind of access
The rule that runs actual_server_info 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_server_info, this is the rule to start with:
actual_server_info is read-only, so it stays allowed. 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_server_info call is checked against it from then on.
Questions about actual_server_info
Get MCP server version and system information. Returns: - Server version - Server name - Node.js version - MCP SDK version - Actual Budget API version - Total tools available - Uptime Use this to check server status, verify version compatibility, or debug issues. It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.
Register the Actual MCP server in PolicyLayer and add a rule for actual_server_info: 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_server_info 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 actual_server_info 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_server_info. 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_server_info 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