Analyze a CDK project to identify AWS services used. This tool dynamically extracts service information from CDK constructs without relying on hardcoded service mappings.
AI agents call analyze_cdk_project to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static analysis of CDK project files to extract metadata about AWS services used. This is a retrieval operation with no side effects on infrastructure, code, or data. It does not create, modify, delete, execute, or commit financial operations. The lowest severity applies since analyzing code poses minimal risk even if an AI agent misuses it.
From the tool's definition Tool description states it 'dynamically extracts service information from CDK constructs' and 'Analyze a CDK project' — these are read-only operations that retrieve and query information about infrastructure code without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access analyze_cdk_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Valkey, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_cdk_project:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_cdk_project": {}
}
}analyze_cdk_project is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze a CDK project to identify AWS services used. This tool dynamically extracts service information from CDK constructs without relying on hardcoded service mappings. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for analyze_cdk_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 Awslabs Valkey. Nothing to install.
analyze_cdk_project is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_cdk_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.
Set action: deny in the PolicyLayer policy for analyze_cdk_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.
analyze_cdk_project is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Valkey, 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 Awslabs Valkey tools catalogued and risk-classified — across an index of 43,000+ MCP servers.