diff_context

diff_context

Server TempoGraph tempograph
Category Read
Risk class Low
Parameters 00 required

What diff_context does on TempoGraph

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

Why diff_context needs a policy

Despite the empty description, the name and sibling tools indicate this is a code analysis/inspection tool that retrieves contextual information about diffs. The pattern of query tools on this server (architecture, dependencies, etc.) suggests data retrieval without modification. The 'context' framing and analysis-oriented server purpose support Read classification.

From the tool's definition Tool name 'diff_context' suggests retrieval of differences/changes in code context. Part of a code graph engine focused on analysis (siblings: architecture, dependencies, dead_code, hotspots). No description provided.

Questions about diff_context

What does the diff_context tool do? +

diff_context. It is categorised as a Read tool in the TempoGraph MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diff_context? +

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

What risk level is diff_context? +

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

Can I rate-limit diff_context? +

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

How do I block diff_context completely? +

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

What MCP server provides diff_context? +

diff_context is provided by the TempoGraph MCP server (tempograph). 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.