analyze_terraform_project

THE RISK

Low Risk

Why analyze_terraform_project needs a policy

This tool performs static analysis of Terraform configuration files to identify AWS services referenced. It reads and parses infrastructure-as-code declarations to extract metadata. There is no indication it modifies files, executes Terraform commands, provisions infrastructure, or triggers any side effects. The action is purely informational and read-only.

From the tool's definition Tool name 'analyze_terraform_project' and description stating it 'dynamically extracts service information from Terraform resource declarations' indicates a query/analysis operation that retrieves and inspects data without modifying, deleting, or executing…

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

POLICY

How to control analyze_terraform_project

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_terraform_project": {}
  }
}

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

Create a free account and register AWS Labs MySQL 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Labs MySQL 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 delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 AWS Labs MySQL MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about analyze_terraform_project

What does the analyze_terraform_project tool do? +

Analyze a Terraform project to identify AWS services used. This tool dynamically extracts service information from Terraform resource declarations. It is categorised as a Read tool in the AWS Labs MySQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_terraform_project? +

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

What risk level is analyze_terraform_project? +

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

Can I rate-limit analyze_terraform_project? +

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

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

analyze_terraform_project is provided by the AWS Labs MySQL MCP Server MCP server (awslabs.mysql-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 Labs MySQL MCP Server tool call.

Start from AWS Labs MySQL 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 →