google_ads_device_targeting_get

THE RISK

Low Risk

Why google_ads_device_targeting_get needs a policy

This tool retrieves configuration data (device targeting settings) from Google Ads accounts. It performs a read-only query with no side effects, no data modification, no code execution, and no financial impact. The blast radius of misuse is minimal — an agent could only view device targeting configuration, which is informational and non-destructive.

From the tool's definition Tool name contains 'get' and description states 'Get the device targeting state' — a retrieval operation with no modification or execution of external operations.

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

POLICY

How to control google_ads_device_targeting_get

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

policy.json

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

google_ads_device_targeting_get 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 Mureo — 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 Mureo tools

Financial google_ads_budget_reallocation Propose a budget reallocation plan by cutting up to 20% Financial meta_ads_instagram_boost Boosts an organic Instagram post by creating a paid ad Financial meta_ads_page_posts_boost Boosts an existing Facebook Page post by creating a paid Destructive google_ads_callouts_remove Detach a callout asset from a Google Ads campaign by Destructive google_ads_conversions_remove Archive (status=REMOVED) a Google Ads conversion action. Destructive google_ads_keywords_remove Removes (soft-deletes) a single keyword criterion from an ad Destructive google_ads_negative_keywords_remove Removes a single campaign-level negative keyword. Returns the Destructive google_ads_sitelinks_remove Detach a sitelink asset from a Google Ads campaign by

All 185 Mureo 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 google_ads_device_targeting_get

What does the google_ads_device_targeting_get tool do? +

Get the device targeting state for a Google Ads. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google_ads_device_targeting_get? +

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

What risk level is google_ads_device_targeting_get? +

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

Can I rate-limit google_ads_device_targeting_get? +

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

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

google_ads_device_targeting_get is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mureo tool call.

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

CHECK YOUR STACK →