Return the full worked-example doc for the bottling-line paired model — topology (5 machines: Filler/Capper/Labeler/Case Packer/Palletizer, 100 bottles/min, Weibull(30,1) TTF + Weibull(5,1) downtime at the Constraint-Level rollup), the two tracks (CT rollup vs LEDS-Level drill-down to 36 named fa...
Risk signalsBulk/mass operation — affects multiple targets
Part of the ReliaStats server.
Free to start. No card required.
AI agents call describe_bottling_line to retrieve information from ReliaStats 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 describe_bottling_line 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.
{
"version": "1",
"default": "deny",
"tools": {
"describe_bottling_line": {}
}
}See the full ReliaStats policy for all 11 tools.
These attack patterns abuse exactly the kind of access describe_bottling_line gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Return the full worked-example doc for the bottling-line paired model — topology (5 machines: Filler/Capper/Labeler/Case Packer/Palletizer, 100 bottles/min, Weibull(30,1) TTF + Weibull(5,1) downtime at the Constraint-Level rollup), the two tracks (CT rollup vs LEDS-Level drill-down to 36 named failure modes), the 4 build sequences (BS1 → BS4), the file-shape mapping between ReliaSim outputs and ReliaStats modes, and a worked cross-MCP tool chain. Optional 'section' parameter narrows to one H2 section. ANTI-FABRICATION: content is sourced from docs/paired-model-bottling-line.md; every claim references the .aidos files or ChapterRegistry.fs in reliasim-site.. It is categorised as a Read tool in the ReliaStats MCP Server, which means it retrieves data without modifying state.
Register the ReliaStats MCP server in PolicyLayer and add a rule for describe_bottling_line: 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 ReliaStats. Nothing to install.
describe_bottling_line 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 describe_bottling_line 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 describe_bottling_line. 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.
describe_bottling_line is provided by the ReliaStats MCP server (https://reliastats.com/mcp/v1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 ReliaStats 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.