Execute OData queries on analytical models to retrieve aggregated data with dimensions and measures. Supports full OData query syntax: $select (column selection), $filter (WHERE conditions), $orderby (sorting), $top/$skip (pagination), $apply (aggregations with sum/average/min/max/count/groupby)....
AI agents invoke query_analytical_data to trigger actions in SAP Datasphere MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While this tool is primarily read-oriented (retrieving aggregated data), it executes arbitrary OData queries against production SAP Datasphere analytical models. The ability to run full OData query syntax including $apply aggregations and $filter conditions means it triggers external operations whose effects depend on arguments.
From the tool's definition 'Execute OData queries on analytical models to retrieve aggregated data' and 'Supports full OData query syntax: $select, $filter, $orderby, $top/$skip, $apply (aggregations)'
Documented attack patterns abuse exactly the kind of access query_analytical_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAP Datasphere MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_analytical_data:
{
"version": "1",
"default": "deny",
"tools": {
"query_analytical_data": {
"limits": [
{
"counter": "query_analytical_data_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query_analytical_data stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute OData queries on analytical models to retrieve aggregated data with dimensions and measures. Supports full OData query syntax: $select (column selection), $filter (WHERE conditions), $orderby (sorting), $top/$skip (pagination), $apply (aggregations with sum/average/min/max/count/groupby). Perfect for business intelligence, reporting, and data analysis. It is categorised as a Execute tool in the SAP Datasphere MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SAP Datasphere MCP Server MCP server in PolicyLayer and add a rule for query_analytical_data: 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 SAP Datasphere MCP Server. Nothing to install.
query_analytical_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_analytical_data 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 query_analytical_data. 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.
query_analytical_data is provided by the SAP Datasphere MCP Server MCP server (mariodefelipe/sap-datasphere-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAP Datasphere MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 SAP Datasphere MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.