AI agents call prmaat_trust_events to retrieve information from Prmaat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/queries trust event data from a ledger without side effects. It is a read-only data retrieval operation against an audit/trust system, consistent with the Read category (search, list, get, fetch). The incomplete description does not indicate any write, execute, destructive, or financial capabilities.
From the tool's definition Tool name is 'prmaat_trust_events' with description starting 'Read the v0.3.1 Governance Trust ledger for a passport — every typed, weighted,' explicitly using the word 'Read' and describing a ledger query operation with no modification capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read the v0.3.1 Governance Trust ledger for a passport — every typed, weighted,. It is categorised as a Read tool in the Prmaat MCP Server, which means it retrieves data without modifying state.
Register the Prmaat MCP server in PolicyLayer and add a rule for prmaat_trust_events: 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 Prmaat. Nothing to install.
prmaat_trust_events 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 prmaat_trust_events 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 prmaat_trust_events. 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.
prmaat_trust_events is provided by the Prmaat MCP server (prmaat/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 →