Trigger scheduled refresh (POST /refresh/schedule or similar).
AI agents invoke scheduled_refresh to trigger actions in Cube Js 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.
This tool performs an action with external side effects (triggering a scheduled refresh process) rather than merely reading data. It is not destructive (no irreversible deletion), not financial, and not a simple write of user data. It is Execute because it triggers a system operation whose effects depend on timing and backend state.
From the tool's definition 'Trigger scheduled refresh' indicates the tool initiates or modifies a scheduling operation. Combined with the sibling tool 'refresh' and the context of Cube.js (which manages data aggregations and caching), this tool executes a backend operation that…
Documented attack patterns abuse exactly the kind of access scheduled_refresh gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cube Js MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for scheduled_refresh:
{
"version": "1",
"default": "deny",
"tools": {
"scheduled_refresh": {
"limits": [
{
"counter": "scheduled_refresh_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}scheduled_refresh 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.
Trigger scheduled refresh (POST /refresh/schedule or similar). It is categorised as a Execute tool in the Cube Js MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cube Js MCP Server MCP server in PolicyLayer and add a rule for scheduled_refresh: 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 Cube Js MCP Server. Nothing to install.
scheduled_refresh 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 scheduled_refresh 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 scheduled_refresh. 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.
scheduled_refresh is provided by the Cube Js MCP Server MCP server (zsembek/cube.js-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cube Js 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.
10 Cube Js MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.