get_my_awareness
AI agents call get_my_awareness to retrieve information from Cluster Execution MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is uninformative, the tool name pattern 'get_*' strongly suggests data retrieval without side effects. The presence of similar monitoring/status tools on the same server reinforces classification as a Read operation. Confidence is moderate (0.6) due to the empty description; however, there is no evidence it executes code, modifies data, or performs destructive actions.
From the tool's definition Tool name 'get_my_awareness' suggests retrieval of state or status information. The description is empty, but naming convention (get_*) and context within a cluster management server indicate a query-type operation.
Attacks that exploit this kind of access
get_my_awareness. It is categorised as a Read tool in the Cluster Execution MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cluster Execution MCP Server MCP server in PolicyLayer and add a rule for get_my_awareness: 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 Cluster Execution MCP Server. Nothing to install.
get_my_awareness 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 get_my_awareness 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 get_my_awareness. 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.
get_my_awareness is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →