Low Risk

search_by_patient_id

search_by_patient_id

How to control search_by_patient_id ↓

What search_by_patient_id does on Amazon ECS MCP Server

AI agents call search_by_patient_id to retrieve information from Amazon ECS 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 search_by_patient_id needs a policy

The tool name contains 'search', which is a read operation. While the empty description reduces confidence, the semantics of searching by an ID typically implies querying a database or data store to retrieve patient records without side effects.

From the tool's definition Tool name 'search_by_patient_id' indicates a retrieval operation that queries data by patient identifier. The description is empty, limiting ability to confirm scope, but the name strongly suggests a search/retrieval function with no modification or deletion.

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

How to control search_by_patient_id

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

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

search_by_patient_id 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 ECS 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 search_by_patient_id

What does the search_by_patient_id tool do? +

search_by_patient_id. It is categorised as a Read tool in the Amazon ECS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_patient_id? +

Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for search_by_patient_id: 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 ECS MCP Server. Nothing to install.

What risk level is search_by_patient_id? +

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

Can I rate-limit search_by_patient_id? +

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

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

search_by_patient_id is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-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 ECS MCP Server tool call.

Start from Amazon ECS 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 ECS 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.