portal_logs_settings_update · ArcGIS MCP: Risk & Policy

WHAT IT DOES

What portal_logs_settings_update does on ArcGIS MCP

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

WHY IT NEEDS A POLICY

Why portal_logs_settings_update needs a policy

The tool modifies portal logging settings, which is a write operation that creates or modifies configuration data. While the description is empty (lowering confidence slightly), the name clearly indicates it updates settings rather than executing arbitrary operations, deleting data, or moving money.

From the tool's definition Tool name 'portal_logs_settings_update' indicates modification of logging configuration settings in an ArcGIS portal environment. The 'update' verb suggests reversible data modification rather than deletion or code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

portal_logs_settings_update Rate-limited

portal_logs_settings_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": {
    "portal_logs_settings_update": {
      "limits": [
        {
          "counter": "portal_logs_settings_update_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 ArcGIS MCP, so you can run agents against it safely.

FAQ

Questions about portal_logs_settings_update

What does the portal_logs_settings_update tool do? +

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

How do I enforce a policy on portal_logs_settings_update? +

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

What risk level is portal_logs_settings_update? +

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

Can I rate-limit portal_logs_settings_update? +

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

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

portal_logs_settings_update is provided by the ArcGIS MCP server (renemorenow/arcgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.