Return current discovery, download, and audit summary.
AI agents call get_project_status to retrieve information from UserGate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation that retrieves and returns status summaries without creating, modifying, deleting, or executing external operations. It falls squarely within the Read category as a data retrieval function. The low severity reflects minimal blast radius—an agent misusing this tool would only gain visibility into project status, not compromise systems or data.
From the tool's definition Tool name 'get_project_status' and description 'Return current discovery, download, and audit summary' indicate retrieval of status/summary information with no modification or side effects.
Attacks that exploit this kind of access
Return current discovery, download, and audit summary. It is categorised as a Read tool in the UserGate MCP MCP Server, which means it retrieves data without modifying state.
Register the UserGate MCP server in PolicyLayer and add a rule for get_project_status: 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 UserGate MCP. Nothing to install.
get_project_status 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 get_project_status 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 get_project_status. 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.
get_project_status is provided by the UserGate MCP server (neonsummit/usergate-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 →