dsql_lint

THE RISK

Low Risk

Why dsql_lint needs a policy

The name 'dsql_lint' implies static code or query linting (read-only analysis), but with no description available, confidence is low. Linting typically has no side effects, suggesting Read or Other category. Given the ambiguity, Other is assigned with low confidence.

From the tool's definition Tool name 'dsql_lint' suggests a linting/static analysis operation, but the description is empty and uninformative.

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

POLICY

How to control dsql_lint

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dsql_lint": {
      "limits": [
        {
          "counter": "dsql_lint_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

dsql_lint gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register AWS Serverless MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Serverless MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive cancel_logs_insight_query cancel_logs_insight_query Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime

All 805 AWS Serverless MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about dsql_lint

What does the dsql_lint tool do? +

dsql_lint. It is categorised as a Other tool in the AWS Serverless MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on dsql_lint? +

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

What risk level is dsql_lint? +

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

Can I rate-limit dsql_lint? +

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

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

dsql_lint is provided by the AWS Serverless MCP Server MCP server (awslabs.aws-serverless-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 AWS Serverless MCP Server tool call.

Start from AWS Serverless MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →