CheckNetworkSecurity
AI agents call CheckNetworkSecurity 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.
Without a description, the classification relies on the tool name. 'Check' operations typically retrieve or validate state without modification. Given it's a network security tool in a MemoryDB/ElastiCache context, it likely queries security group rules, encryption settings, or network ACLs. The low confidence reflects the missing description; confirmation would require clarification from the server documentation.
From the tool's definition Tool name 'CheckNetworkSecurity' suggests querying or checking network security configuration status. No destructive language (delete, drop, override) or execution language (run, execute, trigger) present.
Attacks that exploit this kind of access
CheckNetworkSecurity. 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 CheckNetworkSecurity: 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.
CheckNetworkSecurity 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 CheckNetworkSecurity 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 CheckNetworkSecurity. 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.
CheckNetworkSecurity 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.