List stories via GET /api/v1/stories. WARNING: This endpoint does NOT support OData filtering. All query parameters ($filter, $top, $orderby, etc.) are silently ignored by the SAC API — it always returns every story on the tenant (3000+). The response does NOT include an
AI agents call sac_stories_list to retrieve information from Sap Analytics Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and retrieves story metadata. However, severity is elevated to medium rather than low because the endpoint returns all stories on the tenant (3000+) without filtering support, creating a potential information disclosure risk if an AI agent automatically calls this tool — it could expose sensitive story data to unintended recipients or logs.
From the tool's definition Tool name 'sac_stories_list' and description 'List stories via GET /api/v1/stories' indicate a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access sac_stories_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sap Analytics Cloud, and nothing reaches the server without passing your rules. This is the rule we recommend for sac_stories_list:
{
"version": "1",
"default": "deny",
"tools": {
"sac_stories_list": {}
}
}sac_stories_list 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.
List stories via GET /api/v1/stories. WARNING: This endpoint does NOT support OData filtering. All query parameters ($filter, $top, $orderby, etc.) are silently ignored by the SAC API — it always returns every story on the tenant (3000+). The response does NOT include an. It is categorised as a Read tool in the Sap Analytics Cloud MCP Server, which means it retrieves data without modifying state.
Register the Sap Analytics Cloud MCP server in PolicyLayer and add a rule for sac_stories_list: 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 Analytics Cloud. Nothing to install.
sac_stories_list 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 sac_stories_list 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 sac_stories_list. 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.
sac_stories_list is provided by the Sap Analytics Cloud MCP server (jumenengels/sap_analytics_cloud_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sap Analytics Cloud, 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.
90 Sap Analytics Cloud tools catalogued and risk-classified — across an index of 43,000+ MCP servers.