// SCAN REPORT

Updsts

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 02/07/2026

How to control Updsts ↓

TOOL MAP

What Updsts exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Updsts tools

Write · High updsts_update_sts_credential This tool creates or modifies AWS credential files with STS tokens.

1 of Updsts's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Updsts

PolicyLayer is an MCP gateway — it sits between your AI agents and Updsts, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "updsts_update_sts_credential": {
    "limits": [
      {
        "counter": "updsts_update_sts_credential_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "updsts_get_credential_info": {
    "limits": [
      {
        "counter": "updsts_get_credential_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Updsts — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON UPDSTS →

Instant setup, no code required.

FULL CATALOGUE

All 3 Updsts tools

WRITE 1 tools

Write updsts_update_sts_credential updsts_update_sts_credential

READ 2 tools

Read updsts_get_credential_info updsts_get_credential_info Read updsts_get_credential_info_list updsts_get_credential_info_list

FAQ

Questions about Updsts

How do I prevent bulk modifications through Updsts? +

The Updsts server has 1 write tools including updsts_update_sts_credential. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Updsts.

How many tools does the Updsts MCP server expose? +

3 tools across 2 categories: Read, Write. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Updsts? +

Register the Updsts MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Updsts tool call.

Deterministic rules across all 3 Updsts tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON UPDSTS →

Instant setup, no code required.

3 Updsts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.