Low Risk

weeks_between

Calculate the number of weeks between two dates

Part of the Weekness — Week & Calendar Utilities server.

weeks_between is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE WEEKNESS — WEEK & CALENDAR UTILITIES →

Free to start. No card required.

AI agents call weeks_between to retrieve information from Weekness — Week & Calendar Utilities without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though weeks_between only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "weeks_between": {}
  }
}

See the full Weekness — Week & Calendar Utilities policy for all 8 tools.

Get this rule live on your own Weekness — Week & Calendar Utilities server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WEEKNESS — WEEK & CALENDAR UTILITIES →

These attack patterns abuse exactly the kind of access weeks_between gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so weeks_between only ever does what you allow.

SECURE WEEKNESS — WEEK & CALENDAR UTILITIES →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the weeks_between tool do? +

Calculate the number of weeks between two dates. It is categorised as a Read tool in the Weekness — Week & Calendar Utilities MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on weeks_between? +

Register the Weekness — Week & Calendar Utilities MCP server in PolicyLayer and add a rule for weeks_between: 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 Weekness — Week & Calendar Utilities. Nothing to install.

What risk level is weeks_between? +

weeks_between is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit weeks_between? +

Yes. Add a rate_limit block to the weeks_between 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 weeks_between completely? +

Set action: deny in the PolicyLayer policy for weeks_between. 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 weeks_between? +

weeks_between is provided by the Weekness — Week & Calendar Utilities MCP server (oci:ghcr.io/dvdksn/weekness:1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Weekness — Week & Calendar Utilities tool call.

Deterministic rules across all 8 Weekness — Week & Calendar Utilities tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.