Check if there is enough evidence to decide yet and list missing proof. Use before decision_check when evidence may be thin.
Risk signalsHandles credentials or secrets (api_key) · Accepts raw HTML/template content (payload)
Part of the MVR API - Minimum Viable Relationships server.
Free to start. No card required.
AI agents call mvr_evidence_completeness to retrieve information from MVR API - Minimum Viable Relationships 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 mvr_evidence_completeness 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": {
"mvr_evidence_completeness": {}
}
}See the full MVR API - Minimum Viable Relationships policy for all 19 tools.
These attack patterns abuse exactly the kind of access mvr_evidence_completeness 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.
Check if there is enough evidence to decide yet and list missing proof. Use before decision_check when evidence may be thin.. It is categorised as a Read tool in the MVR API - Minimum Viable Relationships MCP Server, which means it retrieves data without modifying state.
Register the MVR API - Minimum Viable Relationships MCP server in PolicyLayer and add a rule for mvr_evidence_completeness: 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 MVR API - Minimum Viable Relationships. Nothing to install.
mvr_evidence_completeness 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 mvr_evidence_completeness 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 mvr_evidence_completeness. 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.
mvr_evidence_completeness is provided by the MVR API - Minimum Viable Relationships MCP server (https://africanmarketos.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 MVR API - Minimum Viable Relationships 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.