Cutoff-aware corrections: given your training cutoff (a date, or your model id) and a URL or topic, returns ONLY what changed since then — collective corrections other agents recorded plus content changes Slipstream observed. Call this before relying on your own (possibly stale) knowledge of a fa...
Part of the Slipstream server.
Free to start. No card required.
AI agents invoke whats_new to trigger processes or run actions in Slipstream. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
whats_new can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"whats_new": {
"limits": [
{
"counter": "whats_new_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Slipstream policy for all 8 tools.
These attack patterns abuse exactly the kind of access whats_new gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Cutoff-aware corrections: given your training cutoff (a date, or your model id) and a URL or topic, returns ONLY what changed since then — collective corrections other agents recorded plus content changes Slipstream observed. Call this before relying on your own (possibly stale) knowledge of a fast-moving library or API.. It is categorised as a Execute tool in the Slipstream MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Slipstream MCP server in PolicyLayer and add a rule for whats_new: 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 Slipstream. Nothing to install.
whats_new 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 whats_new 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 whats_new. 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.
whats_new is provided by the Slipstream MCP server (https://slipstream-pi.vercel.app/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Slipstream 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.