Low Risk

get_tags

get_tags

How to control get_tags ↓

What get_tags does on Pinboard MCP Server

AI agents call get_tags to retrieve information from Pinboard MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_tags needs a policy

This tool retrieves or lists tags associated with Pinboard bookmarks without modifying, deleting, or executing external operations. The verb 'get_' combined with the Pinboard context where tags are metadata for bookmarks confirms this is a read-only query operation. Low severity due to limited blast radius of tag data exposure.

From the tool's definition Tool name 'get_tags' with context showing it is a sibling to 'add_bookmark', 'get_bookmarks', 'rename_tag', 'suggest_tags', and 'update_bookmark'. The 'get_' prefix and absence of modification/deletion language indicates a retrieval operation.

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

How to control get_tags

PolicyLayer is an MCP gateway — it sits between your AI agents and Pinboard 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.

  1. Create a free account and register Pinboard MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_tags

What does the get_tags tool do? +

get_tags. It is categorised as a Read tool in the Pinboard MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tags? +

Register the Pinboard 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 Pinboard 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 Pinboard MCP Server MCP server (vicgarcia/pinboard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pinboard MCP Server tool call.

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

Free to start. No card required.

6 Pinboard MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.