get_dmarc_policy
Get DMARC policy configuration for a domain
This record as markdown: /tools/cbrown35-20i-mcp/get-dmarc-policy.md
What get_dmarc_policy does on 20i MCP Server
AI agents call get_dmarc_policy to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dmarc_policy is rated Low
This tool queries domain DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy information. The verb 'Get' and lack of any write/delete/execute keywords confirm this is a read-only operation that retrieves configuration without side effects. Even if an AI agent misuses this, it only accesses existing DNS security policy metadata, posing minimal risk.
From the tool's definition Tool name and description indicate retrieval operation: 'Get DMARC policy configuration' — reads existing DMARC policy settings with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs get_dmarc_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dmarc_policy, this is the rule to start with:
get_dmarc_policy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every get_dmarc_policy call is checked against it from then on.
Questions about get_dmarc_policy
Get DMARC policy configuration for a domain. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_dmarc_policy: 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 20i MCP Server. Nothing to install.
get_dmarc_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dmarc_policy 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.
Set action: deny in the PolicyLayer policy for get_dmarc_policy. 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.
get_dmarc_policy is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue