Get local backup status
AI agents call get_local_backup_status to retrieve information from HC3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of local backups without modifying, deleting, or executing any operations. It retrieves information about backup state, which is a typical read operation. The low severity reflects minimal blast radius if misused by an AI agent—it merely exposes backup status information without enabling destructive actions or system modifications.
From the tool's definition Tool name 'get_local_backup_status' and description 'Get local backup status' indicate a retrieval operation with no side effects. The verb 'get' and action of checking status are hallmarks of read-only operations.
Attacks that exploit this kind of access
Get local backup status. It is categorised as a Read tool in the HC3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for get_local_backup_status: 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 HC3 MCP Server. Nothing to install.
get_local_backup_status 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 get_local_backup_status 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 get_local_backup_status. 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.
get_local_backup_status is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). 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 →