bayes
Bayes' Theorem Calculator — Posterior probability P(H|E) from a prior, true-positive rate and false-positive rate.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/bayes.md
What bayes does on Gateway
AI agents call bayes to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
prior | number | Yes | Prior probability P(H), 0..1 |
sensitivity | number | Yes | True-positive rate P(E|H), 0..1 |
false_positive | number | Yes | False-positive rate P(E|not H), 0..1 |
Parameters from the server's own tool schema.
Why bayes is rated Low
This tool performs a statistical/mathematical computation with no side effects. It retrieves no external data, modifies no state, executes no code, deletes nothing, and moves no money. It is a read-like operation in the sense that it transforms inputs to outputs via a deterministic mathematical formula.
From the tool's definition Tool name 'bayes' and description 'Bayes' Theorem Calculator — Posterior probability P(H|E) from a prior, true-positive rate and false-positive rate' indicate a pure mathematical calculation function that takes inputs (prior probability, TPR, FPR) and returns…
Attacks that exploit this kind of access
The rule that runs bayes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bayes, this is the rule to start with:
bayes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every bayes call is checked against it from then on.
Questions about bayes
Bayes' Theorem Calculator — Posterior probability P(H|E) from a prior, true-positive rate and false-positive rate. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
bayes accepts 3 parameters: prior, sensitivity, false_positive. Required: prior, sensitivity, false_positive. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for bayes: 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 Gateway. Nothing to install.
bayes 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 bayes 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 bayes. 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.
bayes is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue