query_actions
Look up previously recorded actions from the audit trail. Use this to check what actions have been taken, verify history, or recall past decisions.
LABSCO SUMMARY
A hash chain is worth only as much as the discipline of writing to it, and record_action asks for the reasoning at the moment the action happens.
The three tools split cleanly: record_action seals what happened together with authorized_by and reasoning, query_actions reads it back filtered by agent or action type, and verify_chain shows that nothing in between was altered by checking that each entry's SHA-256 hash still contains its predecessor's. The tool text is explicit that record_action belongs after every significant action — sending emails, modifying files, running queries, making API calls — which puts the burden on the calling agent rather than on the server, and an action nobody recorded leaves no trace here. What you get in return is narrower and more checkable than a log: a record whose modification is both detectable and locatable.
What it is
An audit-trail server of 3 tools: recording an action with its reasoning and authorisation, querying the recorded history, and verifying the SHA-256 hash chain linking the entries.
What you get
- Records that carry why, not only what: record_action takes action_type, action_params, agent_id, authorized_by and reasoning, so a sealed entry states who authorised the action and on what grounds.
- History readable by agent or by kind of action: query_actions filters on agent_id and action_type under a limit, for checking what has already been done before doing it again.
- Tamper evidence instead of trust: each entry's SHA-256 hash includes the previous entry's hash, and verify_chain walks a given agent_id's chain and reports where the break is if a record was modified.
Requirements
An AgentSeal API key, supplied as AGENTSEAL_API_KEY.
Setup effort
One command plus a key — npx -y agentseal-mcp, then supply credentials
USE CASES
01
Proving after the fact what an agent did
Seal each action with who authorised it and why as it happens, read the history back when somebody asks, and show the chain has not been edited.
02
Checking whether an action was already taken
Query the trail for that agent and that kind of action before repeating it, and record the outcome once it has run.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
record_action
Record an agent action to the AgentSeal audit hash trail. Call this after every significant action (sending emails, modifying files, running queries, making API calls) to create a cryptographically sealed record of what happened and why.
verify_chain
Verify the integrity of the audit trail hash chain. Each entry's SHA-256 hash includes the previous entry's hash — if any record was modified, the chain breaks and this will report where.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- AGENTSEAL_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y agentseal-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"agentseal": {
"command": "npx",
"args": [
"-y",
"agentseal-mcp"
],
"env": {
"AGENTSEAL_API_KEY": "<YOUR_AGENTSEAL_API_KEY>"
}
}
}
}
