Low Risk

extract_placeholders

Extract placeholder {{keys}} from a Google Docs template.

How to control extract_placeholders ↓

What extract_placeholders does on Automagik Tools

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

Low Risk

Why extract_placeholders needs a policy

This tool retrieves and parses placeholder information from a Google Docs template document. It performs a read-only operation that identifies template variables without creating, modifying, or deleting any data. The extraction of metadata about placeholders poses minimal security risk and has no side effects on the document or system state.

From the tool's definition Tool name 'extract_placeholders' and description 'Extract placeholder {{keys}} from a Google Docs template' indicate data retrieval with no modification. The verb 'extract' combined with 'from' denotes querying/reading content from an existing document.

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

How to control extract_placeholders

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_placeholders": {}
  }
}

extract_placeholders 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 Automagik Tools — 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 extract_placeholders

What does the extract_placeholders tool do? +

Extract placeholder {{keys}} from a Google Docs template. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract_placeholders? +

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

What risk level is extract_placeholders? +

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

Can I rate-limit extract_placeholders? +

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

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

extract_placeholders is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Automagik Tools tool call.

Start from Automagik Tools, 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.

122 Automagik Tools 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.