get_tag

THE RISK

Low Risk

Why get_tag needs a policy

The tool retrieves tag information by identifier. This is a query/lookup operation that does not create, modify, delete, or execute any actions. It merely fetches metadata about an existing tag, making it a classic Read operation with minimal risk.

From the tool's definition Tool name 'get_tag' and description 'Get tag details by GUID' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_tag gives an agent:

POLICY

How to control get_tag

PolicyLayer is an MCP gateway — it sits between your AI agents and Evernote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tag:

policy.json

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

get_tag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Evernote MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Evernote MCP Server tools

Destructive delete_note Move a note to trash. Destructive delete_notebook Delete a notebook (moves notes to trash, permanently deletes notebook). Destructive expunge_note Permanently delete a note. Destructive expunge_search Permanently delete a saved search. Destructive expunge_tag Permanently delete a tag. Destructive unset_resource_application_data_entry Remove application data entry from a resource. Write clear_reminder Clear all reminder fields from a note. Write untag_all Remove a tag from all notes.

All 52 Evernote MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_tag

What does the get_tag tool do? +

Get tag details by GUID. It is categorised as a Read tool in the Evernote MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag? +

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

What risk level is get_tag? +

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

Can I rate-limit get_tag? +

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

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

get_tag is provided by the Evernote MCP Server MCP server (kensou24/evernote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Evernote MCP Server tool call.

Start from Evernote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →