AI agents call sp-performance as a supporting operation in CloudWatch Application Signals MCP Server workflows.
With an empty description and an ambiguous name, it is impossible to determine the tool's actual behavior. 'sp-performance' could relate to reading performance metrics, executing queries, or other operations. Given the server context (CloudWatch Application Signals), it likely reads performance data, but confidence is very low. Defaulting to Other with low severity due to insufficient evidence.
From the tool's definition Tool name 'sp-performance' and empty description provide no actionable information about what the tool does.
Documented attack patterns abuse exactly the kind of access sp-performance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CloudWatch Application Signals MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sp-performance:
{
"version": "1",
"default": "deny",
"tools": {
"sp-performance": {
"limits": [
{
"counter": "sp-performance_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} sp-performance gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
sp-performance. It is categorised as a Other tool in the CloudWatch Application Signals MCP Server MCP Server, which means it performs auxiliary operations.
Register the CloudWatch Application Signals MCP Server MCP server in PolicyLayer and add a rule for sp-performance: 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 CloudWatch Application Signals MCP Server. Nothing to install.
sp-performance is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sp-performance 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 sp-performance. 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.
sp-performance is provided by the CloudWatch Application Signals MCP Server MCP server (awslabs.cloudwatch-applicationsignals-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CloudWatch Application Signals MCP Server, 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 CloudWatch Application Signals MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.