AI agents use add_business_days to create or update resources in Shikamaru — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shikamaru environment.
This tool creates or modifies date values based on business day adjustments—a reversible transformation rather than destructive deletion. It qualifies as Write rather than Execute because it performs a deterministic calculation rather than triggering arbitrary external operations or code execution.
From the tool's definition Tool description states it will 'Move a signed number of business days' and performs 'settlement math' on dates. This modifies/transforms date values, creating a new calculated date.
Attacks that exploit this kind of access
Move a signed number of business days under a holiday calendar (settlement math: T+2 is count 2). Zero returns the date unchanged. Deterministic. It is categorised as a Write tool in the Shikamaru MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shikamaru MCP server in PolicyLayer and add a rule for add_business_days: 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.
add_business_days 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 add_business_days 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 add_business_days. 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.
add_business_days 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 →