evidence_update

A write tool on the AbraFlexi MCP server.

SERVERAbraFlexi SOURCEabraflexi-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/abraflexi/evidence-update.md

WHAT IT DOES

What evidence_update does on AbraFlexi

AI agents use evidence_update to create or update resources in AbraFlexi, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AbraFlexi environment.

RISK

Why evidence_update is rated Medium

The 'update' verb indicates a write operation that modifies existing data. Without a description, confidence is reduced, but the pattern of CRUD operations on the 'evidence' resource (evidence_create, evidence_delete, evidence_get, evidence_list, evidence_update) confirms this is a reversible modification tool.

From the tool's definition Tool named 'evidence_update' with no description provided. The naming convention (update) and presence of sibling destructive tools (evidence_delete) suggest this modifies data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs evidence_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AbraFlexi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For evidence_update, this is the rule to start with:

evidence_update Rate-limited

evidence_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "evidence_update": {
      "limits": [
        {
          "counter": "evidence_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AbraFlexi, apply this rule, and every evidence_update call is checked against it from then on.

FAQ

Questions about evidence_update

What does the evidence_update tool do? +

evidence_update is a write tool on the AbraFlexi MCP server. It is categorised as a Write tool in the AbraFlexi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on evidence_update? +

Register the AbraFlexi MCP server in PolicyLayer and add a rule for evidence_update: 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 AbraFlexi. Nothing to install.

What risk level is evidence_update? +

evidence_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit evidence_update? +

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

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

evidence_update is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AbraFlexi, and thousands of servers like it.

This server

All 21 AbraFlexi tools →

Across the catalogue

generate_evidence_manifest on Android Forensics ADB MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →