record_task_artifact

A other tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/record-task-artifact.md

WHAT IT DOES

What record_task_artifact does on Allcanuse

AI agents call record_task_artifact as a supporting operation in Allcanuse workflows.

RISK

Why record_task_artifact is rated Low

With no description, classification relies solely on the name. 'Record' suggests writing/storing data, which would be a Write operation. However, given the context of a system management server with background tasks, and the ambiguity of 'artifact', confidence is low. Most likely a Write operation but cannot confirm without description.

From the tool's definition Tool name is 'record_task_artifact' but description is empty/uninformative. Name suggests saving/storing artifact data associated with a task.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_task_artifact safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_task_artifact, this is the rule to start with:

record_task_artifact Rate-limited

record_task_artifact gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_task_artifact": {
      "limits": [
        {
          "counter": "record_task_artifact_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every record_task_artifact call is checked against it from then on.

FAQ

Questions about record_task_artifact

What does the record_task_artifact tool do? +

record_task_artifact is a other tool on the Allcanuse MCP server. It is categorised as a Other tool in the Allcanuse MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on record_task_artifact? +

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

What risk level is record_task_artifact? +

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

Can I rate-limit record_task_artifact? +

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

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

record_task_artifact is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

my_task on Agent Jail → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →