tap_logout · Tds MCP: Risk & Policy

WHAT IT DOES

What tap_logout does on Tds

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

WHY IT NEEDS A POLICY

Why tap_logout needs a policy

Logout/clearing authorization is a Write operation: it modifies authentication state reversibly. The user can log back in. This is not Destructive (no irreversible deletion), not Execute (no arbitrary command execution), and not Financial. Severity is low because the blast radius is confined to the current session—an agent logging out affects only the active session, not data integrity or broader systems.

From the tool's definition Tool description states it 'reset the user info, clear the authorization info' — operations that modify authentication state but do not delete data irreversibly nor execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tap_logout Rate-limited

tap_logout 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": {
    "tap_logout": {
      "limits": [
        {
          "counter": "tap_logout_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 Tds, so you can run agents against it safely.

FAQ

Questions about tap_logout

What does the tap_logout tool do? +

user wants to logout from TapTap platform or reset the user info, clear the authrization info. It is categorised as a Write tool in the Tds MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tap_logout? +

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

What risk level is tap_logout? +

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

Can I rate-limit tap_logout? +

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

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

tap_logout is provided by the Tds MCP server (@taptap/tds-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.