List prompts from a specific folder or all prompts with pagination
AI agents call list_prompts to retrieve information from Prompteka MCP Server 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 prompt data with pagination support but performs no side effects, creation, modification, or deletion. It is a straightforward data retrieval operation with minimal security risk unless the prompts themselves contain sensitive information, but the tool's function is purely informational.
From the tool's definition Tool name 'list_prompts' and description 'List prompts from a specific folder or all prompts with pagination' indicate retrieval of data without modification. The verb 'list' is a classic Read operation that retrieves and displays existing prompts.
Attacks that exploit this kind of access
List prompts from a specific folder or all prompts with pagination. It is categorised as a Read tool in the Prompteka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prompteka MCP Server MCP server in PolicyLayer and add a rule for list_prompts: 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 Prompteka MCP Server. Nothing to install.
list_prompts 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_prompts 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_prompts. 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_prompts is provided by the Prompteka MCP Server MCP server (webdevguyrg/prompteka-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 →