tdx_tickets_feed_post · TDX MCP Server MCP: Risk & Policy

WHAT IT DOES

What tdx_tickets_feed_post does on TDX MCP Server

AI agents use tdx_tickets_feed_post to create or update resources in TDX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TDX MCP Server environment.

WHY IT NEEDS A POLICY

Why tdx_tickets_feed_post needs a policy

This tool creates new content (a comment/feed entry) on a ticket, which is a Write operation. It modifies ticket state reversibly—comments can be edited or deleted. Severity is medium because posting comments could be misused to spam, harass, or add misleading information to tickets, affecting team communication and decision-making, but the impact is not financial or permanently destructive.

From the tool's definition The tool name is 'tdx_tickets_feed_post' and the description states 'Post a comment to a ticket'. The 'post' operation creates new data (a comment) on an existing ticket, which is a reversible modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdx_tickets_feed_post Rate-limited

tdx_tickets_feed_post stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tdx_tickets_feed_post": {
      "limits": [
        {
          "counter": "tdx_tickets_feed_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TDX MCP Server, so you can run agents against it safely.

FAQ

Questions about tdx_tickets_feed_post

What does the tdx_tickets_feed_post tool do? +

Post a comment to a ticket. It is categorised as a Write tool in the TDX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tdx_tickets_feed_post? +

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

What risk level is tdx_tickets_feed_post? +

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

Can I rate-limit tdx_tickets_feed_post? +

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

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

tdx_tickets_feed_post is provided by the TDX MCP Server MCP server (uidaho-nsummers/tdx-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.