get_email_headers

Get complete email headers for technical analysis

SERVERCowork Bench SOURCE0717376/cowork_bench

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-bench/get-email-headers.md

WHAT IT DOES

What get_email_headers does on Cowork Bench

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

RISK

Why get_email_headers is rated Low

This tool retrieves email header information for analysis purposes. While it is a Read operation (no side effects), the medium severity reflects that email headers can contain sensitive information such as sender details, routing information, and metadata that could be exploited if an agent misuses the tool to extract or aggregate sensitive data.

From the tool's definition Tool name is 'get_email_headers' and description states 'Get complete email headers for technical analysis'. The verb 'get' and action of retrieving email headers indicates data retrieval with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_email_headers safely

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

get_email_headers Allowed

get_email_headers 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": {
    "get_email_headers": {}
  }
}

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

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

FAQ

Questions about get_email_headers

What does the get_email_headers tool do? +

Get complete email headers for technical analysis. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_email_headers? +

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

What risk level is get_email_headers? +

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

Can I rate-limit get_email_headers? +

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

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

get_email_headers is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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