Create an immutable evidence snapshot of the current Everything Report for a domain. Returns a snapshot ID, ISO timestamp, SHA-256 content hash, and stable bookmarkable URLs for both JSON and Markdown renderings of the report. Snapshots are write-once and resolve to the same evidence months/years...
AI agents use create_report_snapshot to create or update resources in Intodns — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intodns environment.
The tool creates new records (snapshots) that are stored persistently and reversibly—they can be created, read, and presumably managed/deleted without irreversible consequence to the underlying domain data. The description explicitly states snapshots are 'write-once' and resolve stably, indicating append-only record creation rather than destructive operations.
From the tool's definition POST creates one snapshot per call (not idempotent); write-once snapshots with stable IDs and timestamps; creates immutable evidence records
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create an immutable evidence snapshot of the current Everything Report for a domain. Returns a snapshot ID, ISO timestamp, SHA-256 content hash, and stable bookmarkable URLs for both JSON and Markdown renderings of the report. Snapshots are write-once and resolve to the same evidence months/years later — useful for tickets, audit trails, NIS2/ISO compliance evidence, and LLM citations that should not drift. POST creates one snapshot per call (not idempotent); use get_report_snapshot to read back. Use this instead of get_everything_report when the result must remain stable. It is categorised as a Write tool in the Intodns MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intodns MCP server in PolicyLayer and add a rule for create_report_snapshot: 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 Intodns. Nothing to install.
create_report_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_report_snapshot 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 create_report_snapshot. 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.
create_report_snapshot is provided by the Intodns MCP server (rosconl/intodns-mcp-server). 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 →