watchpoint_history

Get complete write history for a memory address across the trace (reads all writes before and after current focus)

Server Pernosco jnjaeschke/pernosco-mcp
Category Read
Risk class Low
Parameters 00 required

What watchpoint_history does on Pernosco

AI agents call watchpoint_history to retrieve information from Pernosco without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why watchpoint_history needs a policy

This tool reads/queries historical write events from a debugging trace without modifying any data or executing any code. It is purely a data retrieval operation against a recorded execution trace.

From the tool's definition 'Get complete write history for a memory address across the trace (reads all writes before and after current focus)'

Questions about watchpoint_history

What does the watchpoint_history tool do? +

Get complete write history for a memory address across the trace (reads all writes before and after current focus). It is categorised as a Read tool in the Pernosco MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on watchpoint_history? +

Register the Pernosco MCP server in PolicyLayer and add a rule for watchpoint_history: 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 Pernosco. Nothing to install.

What risk level is watchpoint_history? +

watchpoint_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit watchpoint_history? +

Yes. Add a rate_limit block to the watchpoint_history 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.

How do I block watchpoint_history completely? +

Set action: deny in the PolicyLayer policy for watchpoint_history. 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.

What MCP server provides watchpoint_history? +

watchpoint_history is provided by the Pernosco MCP server (jnjaeschke/pernosco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.