ADACTION
DOCK

ACTIONDOCK FIELD NOTES

AI Agent API Allowlists: Restrict Methods and Exact Paths

Configure exact API path rules for AI agents, check method combinations, and test denied requests before enabling human-approved writes in ActionDock.

A brass cylindrical probe fits a circular opening in a steel plate beside square and triangular probes.

To limit an AI agent to specific API operations, fix the HTTPS destination, allow only the required HTTP methods, and choose exact path rules for endpoints that must exclude child routes. Check every combination of allowed method and path. Keep the provider credential narrowly scoped, and require human approval of each proposed write.

In ActionDock, a rule such as =/catalog/items/42 permits that literal request path. A prefix such as /catalog/items/ includes the collection and its descendants. Both are enforced in the manual_only and manual_and_ai write modes. The following examples show how to choose a scope and verify it before an agent uses it.

Start with the operation the agent needs

Write down the actual request from the provider’s documentation, including the method, path, query and body. For a catalog-maintenance task, that might be PATCH /catalog/items/42 to update a restock date. Check which other changes the same endpoint and credential can perform.

Use the narrowest provider permission available, then configure the gateway’s method and path rules. OWASP recommends allowing only permitted HTTP methods and checking the caller’s authority for the method on the relevant resource. OWASP REST Security Cheat Sheet

For the examples below, assume a connection with the illustrative base URL https://api.example.com/. Replace it with your supported, owner-authorized provider. ActionDock compares path rules against the relative request path. If your base URL includes a path such as /v1/, inspect the resulting full target URL in the approval preview as well.

Choose an exact path or a resource prefix

In the dashboard’s Connections form, Allowed paths accepts one rule per line. The API keeps the field name allowedPathPrefixes for both rule types.

Configured rule Paths permitted by this rule
=/catalog/items/42 Only /catalog/items/42
=/catalog/items/42/ Only /catalog/items/42/, including its final slash
/catalog/items/42/ /catalog/items/42 and descendants such as /catalog/items/42/history
/catalog/items/ The collection root and every descendant, including other item IDs

The leading = belongs in the saved rule. The agent submits path: "/catalog/items/42". Matching is case-sensitive. Exact rules preserve trailing slashes and use literal path spelling, without wildcard expansion or URI-decoding aliases. Use the provider’s documented spelling.

Rules are alternatives. If the same connection contains both =/catalog/items/42 and /catalog/, the broader prefix still admits other catalog paths. Remove broad alternatives when narrowing an existing connection. Previously stored prefixes retain their behavior until the owner edits them. ActionDock agent documentation

Check how methods combine with paths

Rules without a method apply to every method selected on the connection. To limit a rule to one method, prefix it with that enabled method and a space.

Suppose you intend to permit two operations:

On a connection with both methods enabled, save GET =/catalog/items and PATCH =/catalog/items/42 to permit those pairs. PATCH /catalog/items and GET /catalog/items/42 fail these rules. Adding an unmarked broader rule would also permit its method-and-path combinations. Provider permissions and the provider’s own API behavior still apply.

For this read-and-update workflow, these configuration fields express the intended scope:

{
  "allowedMethods": ["GET", "PATCH"],
  "allowedPathPrefixes": ["GET =/catalog/items", "PATCH =/catalog/items/42"],
  "writePolicyMode": "manual_only"
}

This is a connection-policy fragment. Add the destination and credential through the owner connection setup. In manual_only, deterministic path rules apply. manual_and_ai also applies those rules and adds a probabilistic reasonableness check after owner approval. The advanced ai_only mode relies on that AI check for write-path decisions and disables GET access. Choose a mode with manual rules when an exact endpoint allowlist is required. Deterministic policy and AI checks

Review query parameters and body values separately

An exact path rule limits endpoint eligibility. Query values and JSON fields still need review. On an allowed PATCH /catalog/items/42, a proposed body could change a restock date, a price, or several fields together, depending on the provider API.

Put query parameters in the request’s query object. Review the full target URL, method, query and body in the approval preview. Use field-level provider permissions or validation where the provider supports them. ActionDock’s current deterministic path rules leave business-field authorization to those provider controls and the owner’s request review.

Every routed integration.execute write requires the signed-in workspace owner’s approval. Editing a connection’s scope changes its version, so prepare a fresh proposal for review after the edit. Keep provider credentials on the server, and remove alternate direct access if the agent’s writes are meant to pass through the gateway. API access with server-held credentials

Test the requests that should be denied

For the single-item policy above, verify that PATCH /catalog/items/42 can reach owner review. Then use a disposable test environment to check the boundaries:

ActionDock’s path and method checks run during preview creation and again on the execution path. An allowlist denial must leave the provider untouched. A successful Test GET exercises a permitted read and its saved result. Test write approval and denial through the write workflow as well. Testing API writes before production

A recent advisory shows why these boundary tests matter. On November 10, 2026, AWS disclosed incorrect operation-name normalization in the custom security policy of locally run AWS API MCP Server versions 0.2.13 through 1.5.0. Certain names with consecutive capital letters failed to match configured deny or elicitation entries. The maintainer identifies version 1.5.1 as patched and specifies the affected deployment conditions. Follow that upgrade guidance for affected installations. The engineering lesson for a REST gateway is to verify the request forms that policy should refuse, alongside the intended allowed request. AWS security bulletin · Maintainer advisory and scope

Save the chosen scope together with the allowed and denied test cases. Recheck them whenever the provider changes its API or you edit the connection. ActionDock controls requests routed through its MCP or HTTP API, so review the agent’s other credentials and tools as part of deciding which access it needs.