Execute the full governance 360 loop on HTML content: extract governance block → verify signature + content hash → check usage terms → create signed access receipt. This is what an agent calls on every page it reads.
AI agents invoke governance_360 to trigger actions in Agent Passport System — Cryptographic Identity for AI Agents. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | Full HTML of the page |
sourceUrl | string | Yes | URL of the page |
contentBody | string | Yes | Article text content (for hash verification) |
intendedUsage | string | Yes | |
agentPublicKey | string | Yes | Your agent's Ed25519 public key (hex) |
agentPrivateKey | string | Yes | Your agent's Ed25519 private key (hex) |
publisherPublicKey | string | Yes | Publisher's Ed25519 public key (hex) |
Parameters from the server's own tool schema.
Although the tool's primary stated purpose is verification and audit on page reads (which might seem like Read), the explicit use of 'Execute' in the description combined with the multi-step operations (signature verification, hash checking, access receipt creation) that are triggered by agent input and whose side effects depend on the HTML content supplied, classifies this as Execute.
From the tool's definition Tool description explicitly states 'Execute the full governance 360 loop' and 'extract governance block → verify signature + content hash → check usage terms → create signed access receipt.' This comprises multiple operations including verification, hashing,…
Risk signalsAccepts raw HTML/template content (html) · Bulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access governance_360 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for governance_360:
{
"version": "1",
"default": "deny",
"tools": {
"governance_360": {
"limits": [
{
"counter": "governance_360_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}governance_360 stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 150 Agent Passport System — Cryptographic Identity for AI Agents tools →
Execute the full governance 360 loop on HTML content: extract governance block → verify signature + content hash → check usage terms → create signed access receipt. This is what an agent calls on every page it reads. It is categorised as a Execute tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
governance_360 accepts 7 parameters: html, sourceUrl, contentBody, intendedUsage, agentPublicKey, agentPrivateKey, publisherPublicKey. Required: html, sourceUrl, contentBody, intendedUsage, agentPublicKey, agentPrivateKey, publisherPublicKey. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for governance_360: 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 Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.
governance_360 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the governance_360 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 governance_360. 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.
governance_360 is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Passport System — Cryptographic Identity for AI Agents, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.