DynamoDB Read-Only Server

7 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
7 read-only
7 tools total
Read (7) Write / Execute (0) Destructive / Financial (0)

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

Cap read operations
count-items:
  rules:
    - rate_limit: 60/minute

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

Is the DynamoDB Read-Only Server MCP server safe to use without restrictions? +

The DynamoDB Read-Only Server server is primarily read-only with 7 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the DynamoDB Read-Only Server MCP server expose? +

7 tools across 1 categories: Read. 7 are read-only. 0 can modify, create, or delete data.

How do I add Intercept to my DynamoDB Read-Only Server setup? +

One line change. Instead of running the DynamoDB Read-Only Server server directly, prefix it with Intercept: intercept -c jjikky-dynamo-readonly-mcp.yaml -- npx -y @jjikky/dynamo-readonly-mcp. Download a pre-built policy from policylayer.com/policies/jjikky-dynamo-readonly-mcp and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.