Export the full SharePoint SchemaXml of a list or library. The XML contains every field, view, content type, and JSON formatting definition. Useful for backup or cloning.
AI agents call get_list_schema_xml to retrieve information from SharePoint MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and exports schema metadata from a SharePoint list or library. It has no side effects, does not modify, delete, or execute operations, and does not move data outside the read category. The blast radius of misuse is minimal — an agent could exfiltrate schema structure but cannot alter lists, delete content, or trigger external actions.
From the tool's definition Tool name contains 'get' and description states 'Export the full SharePoint SchemaXml' — retrieves schema metadata without modification. Description explicitly notes use cases are 'backup or cloning', both read-only operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Export the full SharePoint SchemaXml of a list or library. The XML contains every field, view, content type, and JSON formatting definition. Useful for backup or cloning. It is categorised as a Read tool in the SharePoint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for get_list_schema_xml: 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 SharePoint MCP Server. Nothing to install.
get_list_schema_xml 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_list_schema_xml 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_list_schema_xml. 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_list_schema_xml is provided by the SharePoint MCP Server MCP server (lukassevcik/sharepoint-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 →