select · Autoconsent MCP: Risk & Policy

WHAT IT DOES

What select does on Autoconsent MCP

AI agents invoke select to trigger actions in Autoconsent MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why select needs a policy

This tool performs a browser automation action (selecting an HTML SELECT element), which constitutes executing an external operation in a real browser environment. While it sounds simple, it interacts with live web pages and can trigger form submissions, page changes, or consent decisions depending on the element selected. It falls under Execute as it triggers browser-side effects beyond mere data retrieval.

From the tool's definition Select an element with SELECT tag — triggers a browser interaction/action on a live browser session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select Rate-limited

select stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select": {
      "limits": [
        {
          "counter": "select_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about select

What does the select tool do? +

Select an element with SELECT tag. It is categorised as a Execute tool in the Autoconsent MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on select? +

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

What risk level is select? +

select is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit select? +

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

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

select is provided by the Autoconsent MCP server (noisysocks/autoconsent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

select is one line of Autoconsent's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →