trace_get

Read a context or memory trace by id.

Server Lore Context Lore-Context/lore-context
Category Read
Risk class Low
Parameters 00 required

What trace_get does on Lore Context

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

Why trace_get needs a policy

This tool retrieves stored trace data by identifier without modifying, deleting, or executing any operations. It is a straightforward query operation with no side effects beyond returning information that has already been stored in the evidence ledger.

From the tool's definition Tool description: 'Read a context or memory trace by id.' The verb 'Read' and the retrieval-only nature (no modification, deletion, or execution) align with the Read category.

Questions about trace_get

What does the trace_get tool do? +

Read a context or memory trace by id. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on trace_get? +

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

What risk level is trace_get? +

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

Can I rate-limit trace_get? +

Yes. Add a rate_limit block to the trace_get 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 trace_get completely? +

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

trace_get is provided by the Lore Context MCP server (Lore-Context/lore-context). 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.