get_portal
Get full configuration details of a Service Portal by sys_id or URL suffix
This record as markdown: /tools/servicenow-mcp-server/get-portal.md
What get_portal does on ServiceNow MCP Server
AI agents call get_portal 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 is rated Low
This tool queries and returns portal configuration details by identifier (sys_id or URL suffix). It performs a read-only retrieval operation with no capacity to modify, delete, or execute actions. Blast radius is limited to information disclosure of portal metadata/configuration.
From the tool's definition Tool name 'get_portal' combined with description 'Get full configuration details' — retrieves configuration data with no mutation or side effects.
Attacks that exploit this kind of access
The rule that runs get_portal 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, this is the rule to start with:
get_portal 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 call is checked against it from then on.
Questions about get_portal
Get full configuration details of a Service Portal by sys_id or URL suffix. 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: 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 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 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. 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 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