AI agents call gsd_audit_uat to retrieve information from Gsd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool scans and reports on unresolved UAT/verification items across phases. This is a purely read/query operation with no writes, executions, or destructive actions. Low severity as misuse would only expose project state information.
From the tool's definition 'Scan all phases for unresolved UAT/verification items' — read-only scanning/querying operation with no modification side effects
Attacks that exploit this kind of access
Scan all phases for unresolved UAT/verification items. It is categorised as a Read tool in the Gsd MCP Server, which means it retrieves data without modifying state.
Register the Gsd MCP server in PolicyLayer and add a rule for gsd_audit_uat: 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 Gsd. Nothing to install.
gsd_audit_uat 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 gsd_audit_uat 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 gsd_audit_uat. 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.
gsd_audit_uat is provided by the Gsd MCP server (m0-ar/gsd-mcp-server). 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 →