marchward_get_decisions
Review recent governance decisions (the audit trail). Filter by agent, tool name, or outcome (ALLOW/BLOCK/ESCALATE). Use to verify governance is active or to investigate what an agent actually did.
This record as markdown: /tools/ai-marchward-mcp-server/marchward-get-decisions.md
What marchward_get_decisions does on Mcp Server
AI agents call marchward_get_decisions to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why marchward_get_decisions is rated Low
This tool retrieves and queries audit trail data with filtering capabilities (by agent, tool name, or outcome) but produces no side effects. It is a read-only inspection mechanism for reviewing historical governance decisions. The blast radius if misused is low—an agent could review audit logs to understand previous decisions, but cannot modify records, execute operations, delete data, or affect financial systems.
From the tool's definition Tool description explicitly states 'Review recent governance decisions' and 'to verify governance is active or to investigate what an agent actually did.' The language 'review' and 'investigate' indicates read-only access to audit logs without modification or…
Attacks that exploit this kind of access
The rule that runs marchward_get_decisions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marchward_get_decisions, this is the rule to start with:
marchward_get_decisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every marchward_get_decisions call is checked against it from then on.
Questions about marchward_get_decisions
Review recent governance decisions (the audit trail). Filter by agent, tool name, or outcome (ALLOW/BLOCK/ESCALATE). Use to verify governance is active or to investigate what an agent actually did. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for marchward_get_decisions: 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 Mcp Server. Nothing to install.
marchward_get_decisions 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 marchward_get_decisions 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 marchward_get_decisions. 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.
marchward_get_decisions is provided by the Mcp Server MCP server (@marchward/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue