schedule_task

A write tool on the Cryptosense MCP server.

SERVERCryptosense SOURCEjosephibra/cryptosense-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/josephibra-cryptosense-mcp/schedule-task.md

WHAT IT DOES

What schedule_task does on Cryptosense

AI agents use schedule_task to create or update resources in Cryptosense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cryptosense environment.

RISK

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 Cryptosense by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs schedule_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cryptosense, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_task": {
      "limits": [
        {
          "counter": "schedule_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cryptosense, apply this rule, and every schedule_task call is checked against it from then on.

FAQ

Questions about schedule_task

What does the schedule_task tool do? +

schedule_task is a write tool on the Cryptosense MCP server. It is categorised as a Write tool in the Cryptosense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_task? +

Register the Cryptosense 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 Cryptosense. Nothing to install.

What risk level is schedule_task? +

schedule_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit schedule_task? +

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.

How do I block schedule_task completely? +

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.

What MCP server provides schedule_task? +

schedule_task is provided by the Cryptosense MCP server (josephibra/cryptosense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cryptosense, and thousands of servers like it.

This server

All 36 Cryptosense tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →sms_schedule on Twilio SMS MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →