evidence_get_record_changes
Get the change history (Prehled zmen zaznamu) of a single record.
This record as markdown: /tools/abraflexi/evidence-get-record-changes.md
What evidence_get_record_changes does on AbraFlexi
AI agents call evidence_get_record_changes to retrieve information from AbraFlexi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why evidence_get_record_changes is rated Low
This tool retrieves change history metadata for a record—a read-only query operation with no side effects. The 'get' verb and explicit mention of retrieving history confirm it performs data retrieval only. While the sibling tools include destructive operations (contact_delete, changes_disable) and financial operations (bank_transaction_create), this specific tool is purely informational.
From the tool's definition Tool name contains 'get' and description states 'Get the change history'; no modification or deletion occurs. Returns historical audit/change data.
Attacks that exploit this kind of access
The rule that runs evidence_get_record_changes 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_get_record_changes, this is the rule to start with:
evidence_get_record_changes 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 AbraFlexi, apply this rule, and every evidence_get_record_changes call is checked against it from then on.
Questions about evidence_get_record_changes
Get the change history (Prehled zmen zaznamu) of a single record. It is categorised as a Read tool in the AbraFlexi MCP Server, which means it retrieves data without modifying state.
Register the AbraFlexi MCP server in PolicyLayer and add a rule for evidence_get_record_changes: 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.
evidence_get_record_changes 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 evidence_get_record_changes 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 evidence_get_record_changes. 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.
evidence_get_record_changes 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.
More on AbraFlexi, and thousands of servers like it.
This server
Across the catalogue