dry_run_attest

Preview which compliance controls a proposed evidence record would earn — without writing

Server Governance Mcp @mima-ai/governance-mcp
Category Read
Risk class Low
Parameters 00 required

What dry_run_attest does on Governance Mcp

AI agents call dry_run_attest to retrieve information from Governance Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why dry_run_attest needs a policy

The tool explicitly performs a dry-run/preview operation and states it operates 'without writing', meaning it only simulates and reads/evaluates what controls would be satisfied. No data is created, modified, or deleted. This is a pure read/query operation with minimal blast radius.

From the tool's definition Preview which compliance controls a proposed evidence record would earn — without writing

Questions about dry_run_attest

What does the dry_run_attest tool do? +

Preview which compliance controls a proposed evidence record would earn — without writing. It is categorised as a Read tool in the Governance Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dry_run_attest? +

Register the Governance MCP server in PolicyLayer and add a rule for dry_run_attest: 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 Governance Mcp. Nothing to install.

What risk level is dry_run_attest? +

dry_run_attest is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dry_run_attest? +

Yes. Add a rate_limit block to the dry_run_attest 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.

How do I block dry_run_attest completely? +

Set action: deny in the PolicyLayer policy for dry_run_attest. 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.

What MCP server provides dry_run_attest? +

dry_run_attest is provided by the Governance MCP server (@mima-ai/governance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

dry_run_attest is one line of Governance's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.