Get full source code (HTML, CSS, client/server scripts) of a Service Portal widget
AI agents call get_portal_widget 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 fetches/queries data (portal widget source code) without side effects. It is a read operation. Severity is medium rather than low because the retrieved source code could contain sensitive logic, credentials, or business logic that could be valuable for adversaries to analyze, though the tool itself only reads and does not execute or modify systems.
From the tool's definition Tool retrieves and retrieves 'full source code (HTML, CSS, client/server scripts)' with no indication of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get full source code (HTML, CSS, client/server scripts) of a Service Portal widget. 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 get_portal_widget: 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.
get_portal_widget 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_portal_widget 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_portal_widget. 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_portal_widget 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 →