Low Risk

esm_kafka_diagnosis

Diagnoses timeout issues in Kafka Event Source Mappings by identifying when they occur. This tool analyzes logs, metrics, and configurations to determine if timeouts happen before reaching the broker, after reaching the broker, or during Lambda processing. It provides specific indicators for eac...

Admin/system-level operation

Part of the AWS Serverless MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call esm_kafka_diagnosis to retrieve information from AWS Serverless MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though esm_kafka_diagnosis only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aws-serverless-mcp-server.yaml
tools:
  esm_kafka_diagnosis:
    rules:
      - action: allow

See the full AWS Serverless MCP Server policy for all 32 tools.

Tool Name esm_kafka_diagnosis
Category Read
Risk Level Low

View all 32 tools →

Agents calling read-class tools like esm_kafka_diagnosis have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the esm_kafka_diagnosis tool do? +

Diagnoses timeout issues in Kafka Event Source Mappings by identifying when they occur. This tool analyzes logs, metrics, and configurations to determine if timeouts happen before reaching the broker, after reaching the broker, or during Lambda processing. It provides specific indicators for each scenario to help pinpoint the root cause. Args: ctx: The execution context Returns: Dict containing diagnostic indicators and next steps for resolving the timeout. It is categorised as a Read tool in the AWS Serverless MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on esm_kafka_diagnosis? +

Add a rule in your Intercept YAML policy under the tools section for esm_kafka_diagnosis. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Serverless MCP Server MCP server.

What risk level is esm_kafka_diagnosis? +

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

Can I rate-limit esm_kafka_diagnosis? +

Yes. Add a rate_limit block to the esm_kafka_diagnosis rule in your Intercept 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 esm_kafka_diagnosis completely? +

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

esm_kafka_diagnosis is provided by the AWS Serverless MCP Server MCP server (awslabs.aws-serverless-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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.