---
title: "Cursor Rules for Marketing: Scope groas MCP Work and Review Every Change"
description: "Build a copyable Cursor rules file for groas MCP: scope accounts, allow-list tools, require change proposals, and verify that no ad changes slipped through."
url: "https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9b3951ae-7734-45c0-8a80-c8dc0894ee71.png"
published: "2026-11-20T16:26:41.975Z"
modified: "2026-11-20T16:26:42.040Z"
---

November 20, 2026 · 10 min read

# Cursor Rules for Marketing: Scope groas MCP Work and Review Every Change

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![A red control dial with a taped note reading "NEVER CHANGE BUDGETS" has been turned anyway, tearing the tape, so a written rule plainly stopped nothing.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9b3951ae-7734-45c0-8a80-c8dc0894ee71.png)

In this article

1. [1. Create an always-applied project rule](#1-create-an-always-applied-project-rule)
2. [2. Scope the run to exact account IDs](#2-scope-the-run-to-exact-account-ids)
3. [3. Allow-list actual MCP tools, not promising-looking prefixes](#3-allow-list-actual-mcp-tools-not-promising-looking-prefixes)
4. [4. Require a proposal before any ad change](#4-require-a-proposal-before-any-ad-change)
5. [5. Give every report and proposal a fixed home](#5-give-every-report-and-proposal-a-fixed-home)
6. [6. Run the read-only acceptance check](#6-run-the-read-only-acceptance-check)
7. [Starter rules file: fill it in, then keep it with the project](#starter-rules-file-fill-it-in-then-keep-it-with-the-project)

An agent connected to an ad account needs standing orders, not another reminder to “be careful.” I use Cursor’s project rules to specify which accounts it may touch, which groas MCP tools it may call, when it must stop, and where the report belongs.

Rules files were built for coding work. The same structure fits marketing work over MCP: a defined scope, a permitted tool set, and an output someone can review. **The important limit: rules instruct the agent; they do not replace tool permissions or approval controls.** A sentence saying “never change budgets” is not an access restriction.

By the end, you will have `.cursor/rules/marketing-orders.mdc`, fixed report and proposal paths, and a read-only test that checks the workflow before you approve a change.

Before starting, have:

- Cursor with Agent mode available.
- groas connected through `mcp.json`, with the agent able to read your ad data.
- One Google Ads or Meta account for the first read-only test.
- That account’s exact ID and access to Cursor’s MCP approval controls.

If the connection is not ready, follow the [Cursor and groas setup walkthrough](https://groas.com/post/running-google-ads-from-cursor-a-marketer-s-guide-to-an) first. Then return here. Connecting the tools and deciding how they may be used are separate jobs.

## 1. Create an always-applied project rule

Create `.cursor/rules/marketing-orders.mdc` in your project root. Use Cursor’s [documented project-rule format and location](https://cursor.com/help/customization/rules), rather than dropping a loose Markdown note somewhere in the repository and hoping the agent finds it.

Paste this starting block:

```mdc
---
description: Scope and approval rules for marketing work via groas MCP
alwaysApply: true
---

## Marketing standing orders
These instructions apply to every marketing task in this project.
They do not grant tool permissions or replace execution approvals.
```

Open `Cursor Settings > Rules` and confirm that `marketing-orders` appears as an always-applied rule. Reload the window if needed. Cursor supports [different rule-loading modes](https://cursor.com/docs/context/rules); this workflow uses `alwaysApply: true` so its instructions do not depend on which file happens to be open.

**Expected result:** the Rules pane shows the file as always applied. Do not treat the agent saying “I read the rules” as your only check.

**Common mistake:** using the wrong extension or relying on a rule that only attaches in particular circumstances. Check the path, extension, and loading mode before rewriting the instructions.

Keep the file short. Cursor recommends rules under 500 lines and references to supporting files rather than pasted copies of everything. Standing orders should be readable enough that you will actually review them.

## 2. Scope the run to exact account IDs

Add the following block. Replace the bracketed brand and example IDs with your own. If you only need Google Ads, remove the Meta entry; do not leave an example account in the finished file.

```markdown
### Scope
- Allowed brand: [Acme Outdoor]
- Allowed accounts: `123-456-7890` (Google Ads), `act_987654` (Meta).
- Use one explicitly identified account per run and per report.
- Default read window: last 28 days unless the prompt specifies otherwise.
- If the requested account ID is not listed, stop and ask.
- If the prompt does not identify one allowed account, ask which account to use.
- Never substitute another account or combine brands in a report.
```

Then ask the agent:

```text
Which account IDs are allowed by this project's marketing rules?
Do not call any tools.
```

**Expected result:** it repeats your listed IDs and makes no tool calls. This checks whether it has the scope instructions, not whether access is technically restricted to those accounts.

**Common mistake:** listing brand names without IDs. Names are useful labels. They are not the identifier to trust when two accounts look similar.

For multi-client work, keep each project folder scoped to one client. That is the useful part of [running multiple accounts through Cursor and groas](https://groas.com/cursor): one working environment, without turning every report into an account-selection exercise.

**Make the account explicit before the first data pull.** A correct analysis of the wrong account is still the wrong deliverable.

## 3. Allow-list actual MCP tools, not promising-looking prefixes

Inspect the MCP servers and tools available in Cursor. Check both `.cursor/mcp.json` and `~/.cursor/mcp.json`: [Cursor supports project and global MCP configuration](https://cursor.com/help/customization/mcp). Do not assume that a minimal project file means no other servers are available.

For this workflow, leave only the needed groas tools available where your configuration allows it. Then inspect their descriptions and copy the exact names of the read tools you intend to use.

Add this block, replacing the bracketed instruction with those names:

```markdown
### Allowed tools
- For marketing tasks, use MCP server `groas` only.
- Approved read tools: [replace with exact tool names reviewed in Cursor].
- Do not infer permission from a tool name or prefix.
- Any unlisted tool requires review before use.
- Any tool that creates, edits, pauses, or changes budgets or bids is a write tool.
- Write tools require the proposal and approval process below.
```

Do not leave the placeholder in place and start a run. A prefix such as `get_*` is convenient shorthand, but it is not a substitute for reviewing what the exposed tool does.

Test the instructions:

```text
List the exact MCP tools permitted for this marketing task.
Separate approved read tools from tools that would require approval.
Do not call any tools.
```

**Expected result:** the answer matches your reviewed list. It does not treat every tool on the groas server as automatically approved.

**Common mistake:** leaving a server available from another project, then assuming the rules file disabled it. **A written allow-list is an instruction, not a server switch.** Use configuration to limit availability and rules to explain the workflow.

Keep the list narrow enough to inspect. More tools are not useful if nobody can tell which ones the agent should call.

## 4. Require a proposal before any ad change

Add the approval block below. Then open `Cursor Settings > Agents > Approvals & Execution` and review the available execution controls alongside Cursor’s [MCP approval guidance](https://cursor.com/help/customization/mcp).

Keep approval prompts enabled for write-capable tools. Do not use `Run Everything` for this workflow. If your controls cannot distinguish reads from writes, keep the broader approval requirement rather than relaxing it to match the convenience of the rules file.

![Clay ad manager holding a stop sign as a robot reaches for a budget dial](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/237027f0-bc0e-4100-9227-b673732fa1e6.png)

```markdown
### Approval rules
- Approved reads may proceed subject to Cursor's execution controls.
- Never execute an ad-account write without explicit human approval.
- First write a proposal to `proposals/YYYY-MM-DD-change.md`.
- Include account ID, campaign, old value > new value, reason, and rollback step.
- Stop after writing the proposal. Do not execute its changes in the same turn.
- Wait for a human message containing `APPROVED` and the proposal's exact path.
- Approval covers only the change described in that file.
- A different change or an edited proposal needs fresh approval.
- New campaigns must be created PAUSED. Activation requires separate approval.
```

Now test the boundary with your scoped account and a named test campaign:

```text
Propose lowering the daily budget on my test campaign to $30.
Write the proposal to the required folder, then stop.
Do not execute any ad-account change.
```

**Expected result:** the agent writes a proposal and stops. It may need approved read calls to identify the campaign and current budget. It must not call a write tool.

**Common mistake:** assuming an automatic review mode knows which business decision you would approve. Execution controls and business approval answer different questions. Keep both.

The file is the point. It puts the account, campaign, and exact change somewhere you can inspect before anything happens. **Approve the proposal, not the agent’s confidence.**

## 5. Give every report and proposal a fixed home

Create `reports/` and `proposals/` in the project root. Add this block:

```markdown
### Where work goes
- Reports: `reports/YYYY-MM-DD-slug.md`.
- Proposals: `proposals/YYYY-MM-DD-change.md`.
- Replace YYYY-MM-DD with the run date.
- Start every file with account ID, date window, and tool calls made.
- Reports include spend, CPA/ROAS where applicable, and top 5 movers.
- Proposals include campaign, old value > new value, reason, and rollback step.
- Write one report file per run.
- Reference prior files by path rather than pasting their full contents into chat.
```

Ask for a report using your actual allowed ID:

```text
Using only approved groas read tools, summarize the last 28 days
for account 123-456-7890. Write one report using the required path
and header. Do not propose or execute any changes.
```

**Expected result:** one dated file in `reports/`, with the account ID, window, and tool-call record at the top. The filename should describe the report, not imply a different reporting period.

**Common mistake:** letting filenames drift into `final-report-v2-new.md`. That tells you someone wanted to finish. It tells you very little about the work.

Use Cursor’s file references when bringing previous work into a later request. A stable path gives the next run something concrete to inspect without filling the conversation with copied reports.

**If the report exists only in chat, the workflow is not finished.** Files give the next review a fixed starting point.

## 6. Run the read-only acceptance check

Use the following prompt in Agent mode. Replace the example account ID before sending it:

```text
Use only the approved groas read tools for account 123-456-7890.
Read the last 28 days.
Write reports/YYYY-MM-DD-test.md, replacing YYYY-MM-DD with today's date.
Propose one budget change in proposals/YYYY-MM-DD-test.md.
Include the current value, proposed value, reason, and rollback step.
Do not execute the change. Stop after writing both files.
```

Review the result in this order:

1. **Check the report header.** Confirm the account ID and date window match the request.
2. **Inspect the actual tool calls in the Agent pane.** Confirm they used the approved groas reads and that zero write calls ran. Do not rely only on the agent’s own tool-call summary.
3. **Open the proposal.** Check the campaign, `old value > new value`, reason, and rollback step.
4. **Confirm the stop.** The agent should wait, not interpret a completed proposal as permission to execute it.

**Expected result:** two files in the right folders, no ad-account writes, and a proposal that can be reviewed without reconstructing the conversation.

**Common mistake:** approving from the chat summary. A neat paragraph can still describe a different campaign from the one in the proposal. Read the file and inspect the tool history.

**If the account is wrong or a write call appears, stop.** Correct the scope, tool availability, or approval controls before running another test. Do not approve a second action to see whether the first problem repeats.

![Diagram showing how a Cursor marketing rule routes reads, reports, proposals, and approvals](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/1321e541-40f3-49e0-a525-7263a2f7ac35.png)

## Starter rules file: fill it in, then keep it with the project

The complete file below brings the steps together. Replace the brand, account IDs, and approved read-tool list. Remove accounts you do not need. Create `reports/` and `proposals/` before the first test.

**Do not run this template with placeholders still inside it.** The useful part is the specific scope you supply, not the existence of a file called _standing orders_.

```mdc
---
description: Scope and approval rules for marketing work via groas MCP
alwaysApply: true
---

## Marketing standing orders
These instructions do not grant permissions or replace execution approvals.

### Scope
- Allowed brand: [replace with brand].
- Allowed accounts: [replace with exact account IDs and platforms].
- One explicitly identified account per run and report. Never combine brands.
- Default window: last 28 days unless the prompt specifies otherwise.
- If the account is missing or not listed, stop and ask. Never substitute.

### Allowed tools
- Marketing MCP server: `groas` only.
- Approved read tools: [replace with exact reviewed tool names].
- Do not infer permission from prefixes. Unlisted tools require review.
- Creates, edits, pauses, budget changes, and bid changes are writes.
- Writes require the approval process below.

### Approval rules
- Approved reads remain subject to Cursor's execution controls.
- Never execute an ad-account write without explicit human approval.
- First write `proposals/YYYY-MM-DD-change.md`.
- Include account, campaign, old value > new value, reason, and rollback.
- Stop after proposing. Do not execute changes in the same turn.
- Wait for human `APPROVED` plus the proposal's exact path.
- Approval covers only that change. Edited proposals need fresh approval.
- Create new campaigns PAUSED. Activation needs separate approval.

### Where work goes
- Replace YYYY-MM-DD with the run date.
- Reports: `reports/YYYY-MM-DD-slug.md`. One report per run.
- Proposals: `proposals/YYYY-MM-DD-change.md`.
- Every file starts with account ID, date window, and tool calls made.
- Reports include spend, CPA/ROAS where applicable, and top 5 movers.
- Reference prior files by path; do not paste their full contents into chat.
```

If the project uses Git, stage the completed rule file:

```sh
git add .cursor/rules/marketing-orders.mdc
```

Staging is not committing. Review and commit the file through your normal project workflow so the instructions travel with the project.

Verify the setup with Step 6: **two files, the correct account, zero write calls, and an always-applied rule in the Rules pane.** That checks this run. Keep reviewing later runs; a successful test does not turn instructions into enforcement.

The first thing I would change after that test passes: set the read window to `last 7 days` for daily checks. A 28-day report is useful context, but it can bury yesterday’s CPA spike. Keep the scope narrow enough to see the decision that needs your attention.

## Frequently Asked Questions

### Does a Cursor rules file actually stop the agent from doing things to my ad account?

No. A Cursor rules file instructs the agent but does not enforce anything on its own. A sentence saying never change budgets is not an access restriction. You still need tool permission configuration and Cursor's execution controls to actually restrict what the agent can do.

### How do I keep the agent from touching the wrong ad account in Cursor?

List the exact account IDs the agent may use in the rules file's Scope section, such as a Google Ads ID like 123-456-7890 or a Meta ID like act_987654, rather than trusting brand names. Require one explicitly identified account per run and report, and instruct the agent to stop and ask if the requested account is not listed. For multi-client work, keep each project folder scoped to one client.

### Should I allow MCP tools by name prefix in my marketing rules?

No. Inspect each tool's description in Cursor and copy its exact name into the rules file's Allowed tools section. A prefix such as get\_\* is convenient shorthand but is not a substitute for reviewing what the tool does. Also check both .cursor/mcp.json and \~/.cursor/mcp.json, because Cursor supports project and global MCP configuration and a server from another project may still be available.

### How does the approval process for changing ads through groas MCP work?

Before any ad-account write, the agent first writes a proposal to proposals/YYYY-MM-DD-change.md containing the account ID, campaign, old value > new value, reason, and a rollback step, then stops. It waits for a human message containing APPROVED plus the proposal's exact path. Approval covers only the change described in that file, so a different change or an edited proposal needs fresh approval, and new campaigns must be created PAUSED.

### Where should agent reports and change proposals be saved?

Reports go to reports/YYYY-MM-DD-slug.md and proposals go to proposals/YYYY-MM-DD-change.md, replacing YYYY-MM-DD with the run date. Every file should start with the account ID, date window, and tool calls made, and there is one report file per run. Reference prior files by path instead of pasting their contents into chat, because a report that exists only in chat means the workflow is not finished.

### How do I test that the Cursor marketing rules are working before approving a change?

Run a read-only prompt that has the agent read the last 28 days, write a test report, propose one budget change, and stop without executing it. Then check the report header for the right account ID and window, inspect the actual tool calls in the Agent pane for zero write calls, read the proposal file, and confirm the agent stopped instead of executing. If a write call appears or the account is wrong, fix the setup before running another test.

### Where do I put the marketing standing orders file in Cursor so the agent always follows it?

Create .cursor/rules/marketing-orders.mdc in the project root with alwaysApply: true, then confirm in Cursor Settings > Rules that it appears as an always-applied rule. Check the path, extension, and loading mode, because a rule that only attaches in some circumstances is a common mistake. Keep the file short; Cursor recommends rules under 500 lines with references to supporting files.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#webpage","url":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp","name":"Cursor Rules for Marketing: Scope groas MCP Work and Review Every Change","description":"Build a copyable Cursor rules file for groas MCP: scope accounts, allow-list tools, require change proposals, and verify that no ad changes slipped through.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9b3951ae-7734-45c0-8a80-c8dc0894ee71.png"},"breadcrumb":{"@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#breadcrumb"},"dateModified":"2026-11-20T16:26:42.040Z","mainEntity":{"@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Cursor Rules for Marketing: Scope groas MCP Work and Review Every Change","item":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#article","url":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp","mainEntityOfPage":{"@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Cursor Rules for Marketing: Scope groas MCP Work and Review Every Change","description":"Build a copyable Cursor rules file for groas MCP: scope accounts, allow-list tools, require change proposals, and verify that no ad changes slipped through.","datePublished":"2026-11-20T16:26:41.975Z","dateModified":"2026-11-20T16:26:42.040Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9b3951ae-7734-45c0-8a80-c8dc0894ee71.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"rules, cursor, mcp, account, groas, tools, change, file","wordCount":2192,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/cursor-rules-for-marketing-work-keep-an-ai-agent-s-mcp#faq","mainEntity":[{"@type":"Question","name":"Does a Cursor rules file actually stop the agent from doing things to my ad account?","acceptedAnswer":{"@type":"Answer","text":"No. A Cursor rules file instructs the agent but does not enforce anything on its own. A sentence saying never change budgets is not an access restriction. You still need tool permission configuration and Cursor's execution controls to actually restrict what the agent can do."}},{"@type":"Question","name":"How do I keep the agent from touching the wrong ad account in Cursor?","acceptedAnswer":{"@type":"Answer","text":"List the exact account IDs the agent may use in the rules file's Scope section, such as a Google Ads ID like 123-456-7890 or a Meta ID like act_987654, rather than trusting brand names. Require one explicitly identified account per run and report, and instruct the agent to stop and ask if the requested account is not listed. For multi-client work, keep each project folder scoped to one client."}},{"@type":"Question","name":"Should I allow MCP tools by name prefix in my marketing rules?","acceptedAnswer":{"@type":"Answer","text":"No. Inspect each tool's description in Cursor and copy its exact name into the rules file's Allowed tools section. A prefix such as get_* is convenient shorthand but is not a substitute for reviewing what the tool does. Also check both .cursor/mcp.json and ~/.cursor/mcp.json, because Cursor supports project and global MCP configuration and a server from another project may still be available."}},{"@type":"Question","name":"How does the approval process for changing ads through groas MCP work?","acceptedAnswer":{"@type":"Answer","text":"Before any ad-account write, the agent first writes a proposal to proposals/YYYY-MM-DD-change.md containing the account ID, campaign, old value > new value, reason, and a rollback step, then stops. It waits for a human message containing APPROVED plus the proposal's exact path. Approval covers only the change described in that file, so a different change or an edited proposal needs fresh approval, and new campaigns must be created PAUSED."}},{"@type":"Question","name":"Where should agent reports and change proposals be saved?","acceptedAnswer":{"@type":"Answer","text":"Reports go to reports/YYYY-MM-DD-slug.md and proposals go to proposals/YYYY-MM-DD-change.md, replacing YYYY-MM-DD with the run date. Every file should start with the account ID, date window, and tool calls made, and there is one report file per run. Reference prior files by path instead of pasting their contents into chat, because a report that exists only in chat means the workflow is not finished."}},{"@type":"Question","name":"How do I test that the Cursor marketing rules are working before approving a change?","acceptedAnswer":{"@type":"Answer","text":"Run a read-only prompt that has the agent read the last 28 days, write a test report, propose one budget change, and stop without executing it. Then check the report header for the right account ID and window, inspect the actual tool calls in the Agent pane for zero write calls, read the proposal file, and confirm the agent stopped instead of executing. If a write call appears or the account is wrong, fix the setup before running another test."}},{"@type":"Question","name":"Where do I put the marketing standing orders file in Cursor so the agent always follows it?","acceptedAnswer":{"@type":"Answer","text":"Create .cursor/rules/marketing-orders.mdc in the project root with alwaysApply: true, then confirm in Cursor Settings > Rules that it appears as an always-applied rule. Check the path, extension, and loading mode, because a rule that only attaches in some circumstances is a common mistake. Keep the file short; Cursor recommends rules under 500 lines with references to supporting files."}}]}]}
```
