schedule_task
A write tool on the Sap Btp Destination MCP server.
This record as markdown: /tools/facusada-mcp-btp/schedule-task.md
What schedule_task does on Sap Btp Destination
AI agents use schedule_task to create or update resources in Sap Btp Destination, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap Btp Destination environment.
Why schedule_task is rated Medium
An AI agent can call schedule_task faster than any human can review: one bad instruction and it creates or modifies resources in Sap Btp Destination by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs schedule_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap Btp Destination, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_task, this is the rule to start with:
schedule_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap Btp Destination, apply this rule, and every schedule_task call is checked against it from then on.
Questions about schedule_task
schedule_task is a write tool on the Sap Btp Destination MCP server. It is categorised as a Write tool in the Sap Btp Destination MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for schedule_task: 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 Btp Destination. Nothing to install.
schedule_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_task 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 schedule_task. 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.
schedule_task is provided by the Sap Btp Destination MCP server (facusada/mcp-btp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap Btp Destination, and thousands of servers like it.
This server
Across the catalogue