get_ms_copilot_topics
List the Virtual Agent topics (sys_cs_topic) that back a Microsoft Copilot integration. Copilot topic mapping itself is configured in Copilot Studio on the Microsoft side, not exposed via ServiceNow REST.
This record as markdown: /tools/servicenow-mcp-server/get-ms-copilot-topics.md
What get_ms_copilot_topics does on ServiceNow MCP Server
AI agents call get_ms_copilot_topics 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_ms_copilot_topics is rated Low
This tool retrieves and lists Virtual Agent topics from ServiceNow's configuration database. The verb 'List' combined with the absence of any modification, deletion, or execution language confirms this is a read-only query operation. The low severity reflects that it only accesses topic metadata/configuration without triggering external actions or exposing sensitive business logic execution.
From the tool's definition Tool description explicitly states it 'List[s]' topics, which is a retrieval operation with 'no' side effects as the description indicates it only reads configuration data that is 'not exposed via ServiceNow REST', implying it queries existing state without…
Attacks that exploit this kind of access
The rule that runs get_ms_copilot_topics 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_ms_copilot_topics, this is the rule to start with:
get_ms_copilot_topics 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_ms_copilot_topics call is checked against it from then on.
Questions about get_ms_copilot_topics
List the Virtual Agent topics (sys_cs_topic) that back a Microsoft Copilot integration. Copilot topic mapping itself is configured in Copilot Studio on the Microsoft side, not exposed via ServiceNow REST. 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_ms_copilot_topics: 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_ms_copilot_topics 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_ms_copilot_topics 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_ms_copilot_topics. 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_ms_copilot_topics 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