list_performance_profiles
List recent performance profiles
This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/list-performance-profiles.md
What list_performance_profiles does on Claude MCP Server Ecosystem
AI agents call list_performance_profiles to retrieve information from Claude MCP Server Ecosystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_performance_profiles is rated Low
This is a simple read/list operation that retrieves performance profile information. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only access performance data that already exists, which is typically non-sensitive infrastructure telemetry.
From the tool's definition Tool name 'list_performance_profiles' and description 'List recent performance profiles' indicate a retrieval operation that queries and returns existing performance data without modifying, executing external operations, or deleting anything.
Attacks that exploit this kind of access
The rule that runs list_performance_profiles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP Server Ecosystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_performance_profiles, this is the rule to start with:
list_performance_profiles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP Server Ecosystem, apply this rule, and every list_performance_profiles call is checked against it from then on.
Questions about list_performance_profiles
List recent performance profiles. It is categorised as a Read tool in the Claude MCP Server Ecosystem MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Ecosystem MCP server in PolicyLayer and add a rule for list_performance_profiles: 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 Claude MCP Server Ecosystem. Nothing to install.
list_performance_profiles 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 list_performance_profiles 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 list_performance_profiles. 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.
list_performance_profiles is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP Server Ecosystem, and thousands of servers like it.
This server
Across the catalogue