Low Risk

archimate_get_audit_log

Read recent entries from the audit log

How to control archimate_get_audit_log ↓

What archimate_get_audit_log does on ArchiMate MCP Server

AI agents call archimate_get_audit_log to retrieve information from ArchiMate MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why archimate_get_audit_log needs a policy

This tool retrieves historical audit log entries without side effects. Audit logs are read-only data sources designed for inspection and compliance purposes. The operation has no impact on the ArchiMate model itself, infrastructure, or data state. Blast radius is minimal—worst case, an AI agent gains visibility into past actions, which is a concern for information disclosure but not for integrity or availability.

From the tool's definition Tool name 'archimate_get_audit_log' and description 'Read recent entries from the audit log' explicitly indicate retrieval of existing audit log data with no modification or deletion.

Documented attack patterns abuse exactly the kind of access archimate_get_audit_log gives an agent:

How to control archimate_get_audit_log

PolicyLayer is an MCP gateway — it sits between your AI agents and ArchiMate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for archimate_get_audit_log:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "archimate_get_audit_log": {}
  }
}

archimate_get_audit_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ArchiMate MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about archimate_get_audit_log

What does the archimate_get_audit_log tool do? +

Read recent entries from the audit log. It is categorised as a Read tool in the ArchiMate MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on archimate_get_audit_log? +

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

What risk level is archimate_get_audit_log? +

archimate_get_audit_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit archimate_get_audit_log? +

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

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

archimate_get_audit_log is provided by the ArchiMate MCP Server MCP server (thijs-hakkenberg/archimate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ArchiMate MCP Server tool call.

Start from ArchiMate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

33 ArchiMate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.