List GRC controls with optional filter by risk or policy
AI agents call list_grc_controls to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves GRC (Governance, Risk, and Compliance) control records from ServiceNow with optional filtering parameters. It has no capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could retrieve sensitive control information but cannot alter systems or data. This is a straightforward read/query operation.
From the tool's definition Tool description states 'List GRC controls' - a retrieval operation with optional filtering. No modifications, deletions, or side effects are mentioned. The verb 'list' and action of filtering existing data are characteristic of read-only operations.
Attacks that exploit this kind of access
List GRC controls with optional filter by risk or policy. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for list_grc_controls: 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 ServiceNow-MCP. Nothing to install.
list_grc_controls 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 list_grc_controls 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 list_grc_controls. 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.
list_grc_controls is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-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 →