filter_instances

Filter EC2 instances based on specified criteria.

SERVERPostgreSQL MCP Server SOURCEaadarshjain/postgres-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/aadarshjain-postgres-mcp-server/filter-instances.md

WHAT IT DOES

What filter_instances does on PostgreSQL MCP Server

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

RISK

Why filter_instances is rated Low

The tool performs filtering and retrieval of EC2 instance information—a read-only operation with no side effects. Filtering is a standard data retrieval operation analogous to the 'list' and 'get' operations mentioned in the server description. No code execution, data modification, deletion, or financial transactions are implied. The low severity reflects minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'filter_instances' and description 'Filter EC2 instances based on specified criteria' indicate a query/search operation that retrieves instance metadata without modifying, deleting, or executing actions on those instances.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filter_instances safely

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

filter_instances Allowed

filter_instances 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": {
    "filter_instances": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every filter_instances call is checked against it from then on.

FAQ

Questions about filter_instances

What does the filter_instances tool do? +

Filter EC2 instances based on specified criteria. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on filter_instances? +

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

What risk level is filter_instances? +

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

Can I rate-limit filter_instances? +

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

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

filter_instances is provided by the PostgreSQL MCP Server MCP server (aadarshjain/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What filter_instances does on PostgreSQL MCP Server

Why filter_instances is rated Low

The rule that runs filter_instances safely

Questions about filter_instances

More on PostgreSQL MCP Server, and thousands of servers like it.