send_digest_email · Local Tech Digest MCP: Risk & Policy

WHAT IT DOES

What send_digest_email does on Local Tech Digest

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

WHY IT NEEDS A POLICY

Why send_digest_email needs a policy

This tool initiates creation and delivery of an email message, which is a reversible write action with side effects (email delivery). It does not execute arbitrary code, delete data, or move money. Severity is medium because uncontrolled email sending could spam users or leak information, but the damage is bounded to email delivery and potentially reparable (e.g., by filtering or disclaiming).

From the tool's definition Tool description states 'Manually trigger a digest email', indicating it creates and sends an email artifact. The word 'send' combined with 'email' confirms a write action that creates new content (the digest) and submits it to an external service (email).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_digest_email Rate-limited

send_digest_email 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": {
    "send_digest_email": {
      "limits": [
        {
          "counter": "send_digest_email_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 Local Tech Digest, so you can run agents against it safely.

FAQ

Questions about send_digest_email

What does the send_digest_email tool do? +

Manually trigger a digest email. mode=. It is categorised as a Write tool in the Local Tech Digest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_digest_email? +

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

What risk level is send_digest_email? +

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

Can I rate-limit send_digest_email? +

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

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

send_digest_email is provided by the Local Tech Digest MCP server (nk1947-sudo/local-tech-digest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.