Low Risk

describe_attachment

describe_attachment

How to control describe_attachment ↓

What describe_attachment does on Amazon Bedrock Knowledge Base Retrieval MCP Server

AI agents call describe_attachment to retrieve information from Amazon Bedrock Knowledge Base Retrieval MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why describe_attachment needs a policy

Based on naming convention alone, 'describe_*' tools typically query and return information about resources without side effects. However, confidence is moderate (0.7) rather than high because the description is empty and cannot confirm the exact behavior.

From the tool's definition Tool name 'describe_attachment' with no description provided. The 'describe' verb pattern strongly suggests a read operation that retrieves metadata or information about an attachment without modification.

Documented attack patterns abuse exactly the kind of access describe_attachment gives an agent:

How to control describe_attachment

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Bedrock Knowledge Base Retrieval MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_attachment:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_attachment": {}
  }
}

describe_attachment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Bedrock Knowledge Base Retrieval MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about describe_attachment

What does the describe_attachment tool do? +

describe_attachment. It is categorised as a Read tool in the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_attachment? +

Register the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server in PolicyLayer and add a rule for describe_attachment: 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 Amazon Bedrock Knowledge Base Retrieval MCP Server. Nothing to install.

What risk level is describe_attachment? +

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

Can I rate-limit describe_attachment? +

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

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

describe_attachment is provided by the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Bedrock Knowledge Base Retrieval MCP Server tool call.

Start from Amazon Bedrock Knowledge Base Retrieval MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.