adobe_logout

TVE: end an Adobe Primetime device session. The device is signed out. Destructive - requires confirm: true in safe mode.

SERVERZype Com SOURCEzype/zype-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/adobe-logout.md

WHAT IT DOES

What adobe_logout does on Zype Com

AI agents call adobe_logout to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`confirm`	boolean	—	Set true to confirm (required in safe mode)
`device_session_id`	string	Yes	Adobe device session ID (required)

Parameters from the server's own tool schema.

RISK

Why adobe_logout is rated Low

Even though adobe_logout only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adobe_logout safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adobe_logout, this is the rule to start with:

adobe_logout Allowed

adobe_logout is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adobe_logout": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every adobe_logout call is checked against it from then on.

FAQ

Questions about adobe_logout

What does the adobe_logout tool do? +

TVE: end an Adobe Primetime device session. The device is signed out. Destructive - requires confirm: true in safe mode. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.

What parameters does adobe_logout accept? +

adobe_logout accepts 2 parameters: confirm, device_session_id. Required: device_session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on adobe_logout? +

Register the Zype Com MCP server in PolicyLayer and add a rule for adobe_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 Zype Com. Nothing to install.

What risk level is adobe_logout? +

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

Can I rate-limit adobe_logout? +

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

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

adobe_logout is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zype Com, and thousands of servers like it.

This server

All 296 Zype Com tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →