Get Copilot content exclusion rules for an organization
AI agents call copilot_get_content_exclusions to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data (content exclusion rules) without modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk if misused by an AI agent, as it only exposes organizational policy information that would typically be accessible to authorized users querying system configuration.
From the tool's definition Tool name 'copilot_get_content_exclusions' with description 'Get Copilot content exclusion rules for an organization' indicates a retrieval operation. The verb 'Get' and lack of modification, deletion, or execution semantics confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access copilot_get_content_exclusions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for copilot_get_content_exclusions:
{
"version": "1",
"default": "deny",
"tools": {
"copilot_get_content_exclusions": {}
}
}copilot_get_content_exclusions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Copilot content exclusion rules for an organization. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for copilot_get_content_exclusions: 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 Sage MCP. Nothing to install.
copilot_get_content_exclusions 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 copilot_get_content_exclusions 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 copilot_get_content_exclusions. 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.
copilot_get_content_exclusions is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.