get-tags

THE RISK

Low Risk

Why get-tags needs a policy

This tool queries and returns tag data without modifying, deleting, or executing any operations. It is a straightforward read operation on task management metadata. The severity is low because tags are typically non-sensitive organizational metadata, and misuse would only expose organizational information structure rather than enabling harmful actions.

From the tool's definition Tool name 'get-tags' and description 'List all tags' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get-tags gives an agent:

POLICY

How to control get-tags

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-tags": {}
  }
}

get-tags 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 Akiflow 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 Akiflow MCP Server tools

Write remove-task-from-timeslot Remove a task from its time slot. Unlinks the task from its associated time slot block. Write unschedule-task Remove a task from the calendar and optionally move to inbox Write add-event Create a new calendar event. Syncs to the source calendar (Google, etc.) Write add-task Create a new task in Akiflow Write add-task-to-timeslot Add a task to a time slot. Links the task to an existing time slot block on the calendar. Write add-time-slot Create a time slot (internal calendar block). Does not sync to external calendars. Write create-task-from-action-item Create an Akiflow task from a meeting recording Write edit-event Edit a calendar event. Changes sync back to the source calendar (Google, etc.)

All 22 Akiflow 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-tags

What does the get-tags tool do? +

List all tags. It is categorised as a Read tool in the Akiflow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-tags? +

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

What risk level is get-tags? +

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

Can I rate-limit get-tags? +

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

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

get-tags is provided by the Akiflow MCP Server MCP server (shrimpwtf/akiflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Akiflow MCP Server tool call.

Start from Akiflow 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 →