site_get

THE RISK

Low Risk

Why site_get needs a policy

This tool retrieves and queries site configuration and capability metadata. The verb 'Get' and the context of reading site details (capabilities, export config) are consistent with Read operations. There is no indication of data modification, deletion, code execution, or financial impact.

From the tool's definition Tool name 'site_get' and description 'Get full details for a specific site including detected capabilities and export config' indicate a retrieval operation with no side effects.

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

POLICY

How to control site_get

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

policy.json

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

site_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 WP Astro MCP — 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 WP Astro MCP tools

Destructive site_remove Deactivate a site (soft delete, can be reactivated). Destructive sync_delete Remove local Markdown files for posts that have been deleted or trashed in WordPress. Also Destructive sync_full Complete content sync: check for changes → pull new/updated posts → delete removed posts → Destructive sync_reset Clear sync tracking data to force a full re-sync on next sync_pull. Does not delete conten Destructive export_cleanup Delete export job data from database (does not delete files). Requires confirm=true. Execute wp_astro_run Execute a WordPress-to-Astro frontend action. Use wp_astro_help to list available actions. Execute export_resume Resume an in-progress export. Processes the next batch of pending posts. Call repeatedly u Execute export_retry Retry all failed posts in an export job.

All 60 WP Astro MCP 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 site_get

What does the site_get tool do? +

Get full details for a specific site including detected capabilities and export config. It is categorised as a Read tool in the WP Astro MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on site_get? +

Register the WP Astro MCP server in PolicyLayer and add a rule for site_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 WP Astro MCP. Nothing to install.

What risk level is site_get? +

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

Can I rate-limit site_get? +

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

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

site_get is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WP Astro MCP tool call.

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

CHECK YOUR STACK →