Medium Risk

context

Get the most relevant knowledge for the current reasoning step, ranked by composite salience (recency × frequency × priority). Returns a token-optimized context window in 'predicate', 'natural', or 'structured' format. Pass goals for goal-driven selection, sessionId for incremental diffs across t...

High parameter count (13 properties)

Part of the Nocturnusai MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

nocturnusai-mcp Write Risk 2/5

AI agents use context to create or modify resources in Nocturnusai. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call context repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Nocturnusai.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

ai-nocturnus-logic-server.yaml
tools:
  context:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Nocturnusai policy for all 16 tools.

Tool Name context
Category Write
Risk Level Medium

View all 16 tools →

Agents calling write-class tools like context have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the context tool do? +

Get the most relevant knowledge for the current reasoning step, ranked by composite salience (recency × frequency × priority). Returns a token-optimized context window in 'predicate', 'natural', or 'structured' format. Pass goals for goal-driven selection, sessionId for incremental diffs across turns. Side effects: read-only for stored facts (salience access counters may update internally). Auth: requires X-Tenant-ID header; FACT_READ permission when auth is enabled. Rate-limited per principal. Errors: VALIDATION_ERROR on bad args.. It is categorised as a Write tool in the Nocturnusai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on context? +

Add a rule in your Intercept YAML policy under the tools section for context. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Nocturnusai MCP server.

What risk level is context? +

context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit context? +

Yes. Add a rate_limit block to the context rule in your Intercept 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 context completely? +

Set action: deny in the Intercept policy for 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 context? +

context is provided by the Nocturnusai MCP server (nocturnusai-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Nocturnusai

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.