List story types, enumerate content types, and filter file repository resources via GET /api/v1/filerepository/Resources. Use to list all story types (standard story, story template, analytic application), enumerate design experiences (Classic vs Optimized), or filter stories/apps by user, date, ...
AI agents call sac_filerepository_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 data retrieval tool with no side effects. However, the applyManagePrivilege flag allows elevation from restricted to ALL tenant content visibility, creating risk if misused by an agent with excessive scope — an AI could exfiltrate comprehensive organizational analytics structure and metadata across the entire tenant, justifying medium rather than low severity.
From the tool's definition Tool uses GET /api/v1/filerepository/Resources to 'list story types, enumerate content types, and filter file repository resources.' Explicitly describes listing and filtering operations with OData query parameters ($filter, $top, $orderby, $select, $count) —…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access sac_filerepository_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_filerepository_list:
{
"version": "1",
"default": "deny",
"tools": {
"sac_filerepository_list": {}
}
}sac_filerepository_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 story types, enumerate content types, and filter file repository resources via GET /api/v1/filerepository/Resources. Use to list all story types (standard story, story template, analytic application), enumerate design experiences (Classic vs Optimized), or filter stories/apps by user, date, or type. OData $filter, $top, $orderby, $select, $count all work. IMPORTANT — visibility scope: By default (applyManagePrivilege=false), only content the service account has Read access to is returned (typically a small subset of tenant content). Set applyManagePrivilege=true to get ALL tenant content (all users. 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_filerepository_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_filerepository_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_filerepository_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_filerepository_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_filerepository_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.