Explain OData query parameters supported by Microsoft Graph: $filter, $select, $expand, $orderby, $top, $count, $search.
AI agents call graph_explain_odata to retrieve information from Ms Graph Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool provides educational/reference information about OData syntax and query parameters used in Microsoft Graph API calls. It does not execute queries, modify data, delete resources, or trigger external operations. It is a documentation or explanation utility that helps users understand how to construct requests.
From the tool's definition Tool name 'graph_explain_odata' and description indicate it explains OData query parameters ($filter, $select, $expand, $orderby, $top, $count, $search).
Attacks that exploit this kind of access
Explain OData query parameters supported by Microsoft Graph: $filter, $select, $expand, $orderby, $top, $count, $search. It is categorised as a Read tool in the Ms Graph Dev MCP Server, which means it retrieves data without modifying state.
Register the Ms Graph Dev MCP server in PolicyLayer and add a rule for graph_explain_odata: 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 Ms Graph Dev. Nothing to install.
graph_explain_odata 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 graph_explain_odata 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 graph_explain_odata. 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.
graph_explain_odata is provided by the Ms Graph Dev MCP server (stubbedev/ms-graph-dev-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 →