TaskRay MCP: What Assistants Can Find and Change Safely

When someone asks their AI assistant for "overdue tasks on the Acme project" or "the projects we finished last quarter", the assistant narrows the list for them. Searching, safety checks and custom fields work the same way across the tools.

In this article:

  • What assistants can find
  • Checks that protect your team's work
  • Custom fields are yours to manage
  • Good to know
  • Frequently asked questions

What Assistants Can Find

A user might ask What the assistant narrows by
"Show me our onboarding projects." Any part of the name, ignoring case
"What's overdue on the Acme project?" One Project, open Tasks only, and an Estimated End Date before today
"Which tasks changed this week?" When records were created or last modified
"Include the projects we've archived." Archived work, which lists leave out unless the user asks
"Show me the implementation projects." Record Type, when your org uses record types

Checks That Protect Your Team's Work

  • If the connection drops, the assistant can resend a request without creating a second record.
  • If a record changed after the assistant read it, the update is refused, and the assistant reads it again first.

Both checks protect a change only when the assistant uses them, except that a change waiting for approval is always checked.

Custom Fields Are Yours to Manage

Assistants read and set only the custom fields you've exposed, as described in Step 3 of TaskRay MCP: Administration Installation & Setup.

  • Allow up to 10 minutes after you expose a field, or up to an hour for a field newly created in Salesforce.
  • Lists never include your org's custom fields.
  • A field the user can't edit in Salesforce stays read-only for their assistant. Formula, roll-up summary and auto-number fields can never be set.
  • When one field in a request can't be written, nothing is saved, and the error names the field.

Good to Know

  • Archived work stays out of lists unless the user asks for it. Templates are handled by the tools in TaskRay MCP Tool Reference: Template Tools. Lists of supporting records, such as Time Entries and Project team members, include template and archived records too.
  • Two users can see different fields on the same record, because field-level security decides what each user can read. A missing field means the user can't read it, not that it's empty.
  • A list reaches about the first 2,200 matching records. For more, the assistant narrows the request.
  • Created and modified dates are counted in UTC, not in the user's time zone.

Frequently Asked Questions

Q. A user says their assistant can't find a Project they know exists. Why?

Great question! The Project may be archived, which lists leave out until the user asks, or a template, which only the template tools find. Otherwise, check the user's access to it in Salesforce, because an assistant sees only what its user can see.

Where to Go Next

Have a question this reference doesn't answer? Not to worry, our Support Team is ready to help! Contact TaskRay Support with what the user asked their assistant to do, the exact error text, and whether the org is production or sandbox.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request