get_portal_widget
Get full source code (HTML, CSS, client/server scripts) of a Service Portal widget
This record as markdown: /tools/servicenow-mcp-server/get-portal-widget.md
What get_portal_widget does on ServiceNow MCP Server
AI agents call get_portal_widget to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_portal_widget is rated Low
This tool retrieves source code of Service Portal widgets. While it is a Read operation (no side effects), the severity is elevated to medium because source code may contain sensitive information such as API keys, authentication logic, business rules, or confidential algorithms that could be weaponized if an AI agent misuses it to exfiltrate or analyze intellectual property or secrets embedded in widget code.
From the tool's definition Tool description states 'Get full source code (HTML, CSS, client/server scripts)' — retrieval-only operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_portal_widget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_portal_widget, this is the rule to start with:
get_portal_widget is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every get_portal_widget call is checked against it from then on.
Questions about get_portal_widget
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 Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server 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 Server. 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 MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue