iam_list_keys

주어진 서비스 계정의 기존 키 목록. keyId / keyType / 만료시간 반환. 회수할 키 찾을 때 사용.

SERVERMimi Seed SOURCE@yoonion/mimi-seed-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yoonion-mimi-seed-mcp/iam-list-keys.md

WHAT IT DOES

What iam_list_keys does on Mimi Seed

AI agents call iam_list_keys to retrieve information from Mimi Seed without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why iam_list_keys is rated Low

This tool retrieves and queries IAM service account keys without modifying or deleting them. It is fundamentally a Read operation. However, severity is elevated to high because: (1) it exposes sensitive authentication credentials metadata that could inform an attacker about the security posture of the account, (2) the context mentions this data is used to 'find keys to revoke,' indicating keys are security-critical,…

From the tool's definition Tool name: iam_list_keys. Description: 'Lists existing keys for a given service account. Returns keyId / keyType / expiration time. Used when finding keys to revoke.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iam_list_keys safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mimi Seed, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iam_list_keys, this is the rule to start with:

iam_list_keys Allowed

iam_list_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "iam_list_keys": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mimi Seed, apply this rule, and every iam_list_keys call is checked against it from then on.

FAQ

Questions about iam_list_keys

What does the iam_list_keys tool do? +

주어진 서비스 계정의 기존 키 목록. keyId / keyType / 만료시간 반환. 회수할 키 찾을 때 사용. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on iam_list_keys? +

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

What risk level is iam_list_keys? +

iam_list_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit iam_list_keys? +

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

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

iam_list_keys is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mimi Seed, and thousands of servers like it.

This server

All 230 Mimi Seed tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →