Medium Risk

markChatConversationRead

Mark a chat conversation as read.

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

AI agents use markChatConversationRead to create or modify resources in Xdevplatform/xmcp. 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 markChatConversationRead 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 Xdevplatform/xmcp.

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

xdevplatform-xmcp.yaml
tools:
  markChatConversationRead:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Xdevplatform/xmcp policy for all 135 tools.

Tool Name markChatConversationRead
Category Write
Risk Level Medium

View all 135 tools →

Agents calling write-class tools like markChatConversationRead 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 markChatConversationRead tool do? +

Mark a chat conversation as read.. It is categorised as a Write tool in the Xdevplatform/xmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on markChatConversationRead? +

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

What risk level is markChatConversationRead? +

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

Can I rate-limit markChatConversationRead? +

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

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

markChatConversationRead is provided by the Xdevplatform/xmcp MCP server (xdevplatform/xmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.