export_results · Azure Log Analytics MCP Server MCP

WHAT IT DOES

What export_results does on Azure Log Analytics MCP Server

AI agents use export_results to create or update resources in Azure Log Analytics MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure Log Analytics MCP Server environment.

WHY IT NEEDS A POLICY

Why export_results needs a policy

This tool creates or writes data to a file system, which is a reversible modification action. While it doesn't delete data, it does persist query results to storage. The blast radius is medium because exporting sensitive log data could expose confidential information if an agent exports logs without proper authorization context, but the action itself is reversible (the exported file can be deleted).

From the tool's definition Tool name 'export_results' and description 'Export query results to file' indicate creation of a new file with query data output.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_results Rate-limited

export_results 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": {
    "export_results": {
      "limits": [
        {
          "counter": "export_results_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure Log Analytics MCP Server, so you can run agents against it safely.

FAQ

Questions about export_results

What does the export_results tool do? +

Export query results to file. It is categorised as a Write tool in the Azure Log Analytics MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_results? +

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

What risk level is export_results? +

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

Can I rate-limit export_results? +

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

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

export_results is provided by the Azure Log Analytics MCP Server MCP server (rasta26/azure_log_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.