AI agents call get_snapshot_status to retrieve information from LegacyMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query the status of snapshots within an Active Directory assessment context. The 'get_' prefix and comparison with sibling tools strongly suggest a read-only operation that retrieves data without side effects. While the empty description reduces confidence slightly, the naming convention and server context support classification as a Read operation with low severity risk.
From the tool's definition Tool name 'get_snapshot_status' indicates a query/status retrieval operation. Description is empty, but the sibling tool 'create_snapshot' and the naming pattern of other 'get_*' tools on this server (get_blocked_inheritance_ous,…
Attacks that exploit this kind of access
get_snapshot_status. It is categorised as a Read tool in the LegacyMCP MCP Server, which means it retrieves data without modifying state.
Register the Legacy MCP server in PolicyLayer and add a rule for get_snapshot_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 LegacyMCP. Nothing to install.
get_snapshot_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_snapshot_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_snapshot_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_snapshot_status is provided by the Legacy MCP server (marco-lelli/legacy-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 →