menese_jobs
Manage on-chain scheduled jobs via your MeneseAgent canister. Jobs persist and execute on-chain (recurring swaps, conditional trades, etc.). Requires an agent canister (set MENESE_AGENT_CANISTER_ID env var).
This record as markdown: /tools/aboodtt404-mcp-menese-sdk/menese-jobs.md
What menese_jobs does on Mcp Menesesdk
AI agents invoke menese_jobs to trigger actions in Mcp Menesesdk. 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.
Why menese_jobs is rated High
This tool triggers execution of persistent, recurring financial transactions (swaps, trades) on a blockchain without direct per-transaction human approval. While it has financial implications (swaps/trades), the primary risk is uncontrolled autonomous execution of code-like instructions on-chain. This is Execute rather than Financial because it orchestrates automated execution logic rather than a direct payment.
From the tool's definition Tool description states it "Manage[s] on-chain scheduled jobs" that "execute on-chain (recurring swaps, conditional trades, etc.)".
Attacks that exploit this kind of access
The rule that runs menese_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Menesesdk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For menese_jobs, this is the rule to start with:
menese_jobs 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Menesesdk, apply this rule, and every menese_jobs call is checked against it from then on.
Questions about menese_jobs
Manage on-chain scheduled jobs via your MeneseAgent canister. Jobs persist and execute on-chain (recurring swaps, conditional trades, etc.). Requires an agent canister (set MENESE_AGENT_CANISTER_ID env var). It is categorised as a Execute tool in the Mcp Menesesdk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Menesesdk MCP server in PolicyLayer and add a rule for menese_jobs: 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 Mcp Menesesdk. Nothing to install.
menese_jobs 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 menese_jobs 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 menese_jobs. 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.
menese_jobs is provided by the Mcp Menesesdk MCP server (aboodtt404/mcp-menese-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Menesesdk, and thousands of servers like it.
Across the catalogue