List attestation history for an assumption.
AI agents call list_attestations to retrieve information from Mipiti MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays attestation history, which is a read-only operation with no side effects. It does not create, modify, delete, or execute external operations. The blast radius is minimal – an AI agent misusing this tool would at worst retrieve sensitive attestation data it shouldn't see, but cannot corrupt the security posture platform or its data.
From the tool's definition Tool name is 'list_attestations' and description states 'List attestation history for an assumption' – this is a retrieval/query operation that returns historical data without modifying or deleting anything.
Attacks that exploit this kind of access
List attestation history for an assumption. It is categorised as a Read tool in the Mipiti MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for list_attestations: 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 Mipiti MCP Server. Nothing to install.
list_attestations 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 list_attestations 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 list_attestations. 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.
list_attestations is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-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 →