Read project context to understand current state. Call this at the START of a new session to resume where you left off. Returns plan answers, docs content, recent history, and quality score.
AI agents call pmpt_read_context to retrieve information from Pmpt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads existing project state information to enable session resumption. It has no capability to modify, delete, or execute operations. The explicit use of 'Read' in both the name and description, combined with the list of read-only return values (answers, content, history, score), clearly places it in the Read category with low severity since it only accesses data without side effects.
From the tool's definition Tool name 'pmpt_read_context' and description explicitly states 'Read project context' and 'Returns plan answers, docs content, recent history, and quality score' — retrieval and querying only, with no mention of modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access pmpt_read_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pmpt, and nothing reaches the server without passing your rules. This is the rule we recommend for pmpt_read_context:
{
"version": "1",
"default": "deny",
"tools": {
"pmpt_read_context": {}
}
}pmpt_read_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read project context to understand current state. Call this at the START of a new session to resume where you left off. Returns plan answers, docs content, recent history, and quality score. It is categorised as a Read tool in the Pmpt MCP Server, which means it retrieves data without modifying state.
Register the Pmpt MCP server in PolicyLayer and add a rule for pmpt_read_context: 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 Pmpt. Nothing to install.
pmpt_read_context 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 pmpt_read_context 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 pmpt_read_context. 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.
pmpt_read_context is provided by the Pmpt MCP server (pmptwiki/pmpt-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pmpt, 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.
14 Pmpt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.