Generate coupon/payment accrual periods between an effective and a termination date: monthly to annual frequency, backward or forward roll, short or long stub, optional end-of-month rule, business-day adjustment per calendar. Returns each period
AI agents call generate_schedule to retrieve information from Shikamaru without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a deterministic calculation to generate a schedule of accrual periods based on input parameters. It reads/computes date math and returns results without modifying any data, executing code with side effects, or committing financial transactions. It is purely a calculation/query tool.
From the tool's definition Generate coupon/payment accrual periods between an effective and a termination date... Returns each period
Attacks that exploit this kind of access
Generate coupon/payment accrual periods between an effective and a termination date: monthly to annual frequency, backward or forward roll, short or long stub, optional end-of-month rule, business-day adjustment per calendar. Returns each period. It is categorised as a Read tool in the Shikamaru MCP Server, which means it retrieves data without modifying state.
Register the Shikamaru MCP server in PolicyLayer and add a rule for generate_schedule: 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 Shikamaru. Nothing to install.
generate_schedule 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 generate_schedule 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 generate_schedule. 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.
generate_schedule is provided by the Shikamaru MCP server (JayOfemi/shikamaru). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →