List available prompt profiles from the prompts directory.
AI agents call list_prompt_profiles to retrieve information from Codeviewer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of prompt profiles from a directory. It performs no mutations, executions, deletions, or financial operations. The action is purely informational retrieval with no side effects, fitting squarely within the Read category. Severity is low because listing available profiles poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_prompt_profiles' and description 'List available prompt profiles from the prompts directory' indicate a read-only retrieval operation that enumerates configuration data without modification.
Attacks that exploit this kind of access
List available prompt profiles from the prompts directory. It is categorised as a Read tool in the Codeviewer MCP Server, which means it retrieves data without modifying state.
Register the Codeviewer MCP server in PolicyLayer and add a rule for list_prompt_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 Codeviewer. Nothing to install.
list_prompt_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_prompt_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_prompt_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_prompt_profiles is provided by the Codeviewer MCP server (master0ffate/codeviewer-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 →