get_prompt
AI agents call get_prompt to retrieve information from Prompt Store MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries prompt data with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The local-only context and personal library nature present minimal blast radius. Low severity assigned because exposure of stored prompts poses limited risk compared to data modification or deletion.
From the tool's definition Tool name 'get_prompt' and server context indicate retrieval of stored prompts from SQLite database. Server description emphasizes it 'stores, search, and manage' prompts with no mention of write/delete operations for this specific tool.
Attacks that exploit this kind of access
get_prompt. It is categorised as a Read tool in the Prompt Store MCP MCP Server, which means it retrieves data without modifying state.
Register the Prompt Store MCP server in PolicyLayer and add a rule for get_prompt: 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 Prompt Store MCP. Nothing to install.
get_prompt 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_prompt 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_prompt. 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_prompt is provided by the Prompt Store MCP server (mhoshdev/prompt-store-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 →