New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_risk_statement

Get full details of a single Risk Statement by sys_id.

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-risk-statement.md

What get_risk_statement does on ServiceNow-MCP

AI agents call get_risk_statement to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_risk_statement is rated Low

This tool retrieves information about a risk statement using a unique identifier (sys_id). It performs a read-only query operation with no capability to modify, delete, or execute actions. The blast radius of misuse is limited to potential unauthorized information disclosure of risk data already stored in ServiceNow, which is a low-severity read vulnerability.

From the tool's definition Tool name 'get_risk_statement' and description 'Get full details of a single Risk Statement by sys_id' indicate a retrieval operation that queries and returns data without modification or side effects.

Questions about get_risk_statement

What does the get_risk_statement tool do? +

Get full details of a single Risk Statement by sys_id. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_risk_statement? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for get_risk_statement: 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.

What risk level is get_risk_statement? +

get_risk_statement is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_risk_statement? +

Yes. Add a rate_limit block to the get_risk_statement 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.

How do I block get_risk_statement completely? +

Set action: deny in the PolicyLayer policy for get_risk_statement. 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.

What MCP server provides get_risk_statement? +

get_risk_statement 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.

More on ServiceNow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.