Files
landing-api/app/Policies/MediaPolicy.php
Josep Piguillem a49816eb46
Some checks failed
Tests / lint (push) Has been cancelled
Tests / test (push) Has been cancelled
Tests / test-postgres (push) Has been cancelled
Tests / mcp (push) Has been cancelled
Upload images through the API, and from the MCP server
POST /api/v1/media stores an image where the panel keeps a page's and
answers with the path to send as `featured_image`. Without it the MCP
server could create a page but never give it a picture. The file goes
through Media::for(), so it is processed, served and pruned like one
uploaded in the panel.

Two ways in, one per request: a multipart `file`, or JSON with a `url`
the API downloads itself. JPEG, PNG, WebP, GIF or AVIF only, decided
from the bytes; no SVG, which is a document that can carry script.

The URL is fetched from inside the stack's network, so RemoteImage
guards it: HTTPS only, every resolved address must be public, the
connection is pinned to the checked address with CURLOPT_RESOLVE so a
changing DNS answer cannot swap in a private one, redirects are not
followed, and the body is read to a ceiling whatever its headers say.

Uploading needs permission to write pages. MediaPolicy::create stays
false, so the panel gains no free-standing "new file" button.

In the MCP server a multipart binary field becomes `<field>_path` over
stdio: the server reads the file from the caller's disk and sends it
as multipart, instead of the model pushing base64 through its context.
Over HTTP the server's disk is not the caller's, so only `body.url` is
offered.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-28 11:16:33 +02:00

47 lines
1.2 KiB
PHP

<?php
declare(strict_types=1);
namespace App\Policies;
use App\Models\User;
class MediaPolicy extends ResourcePolicy
{
protected function resource(): string
{
return 'media';
}
/**
* Files arrive by being uploaded on a record, not by being created here.
*/
public function create(User $user): bool
{
return false;
}
/**
* Uploading through the API, which has no form to attach a file to.
*
* Still true to the rule above in spirit: through the API the one record
* that holds an image is a page, so whoever may write pages may upload the
* image for one — and nobody else, whatever their `media.*` permissions,
* which only ever described looking after files that already exist.
*/
public function upload(User $user): bool
{
return $user->can('pages.create') || $user->can('pages.update');
}
/**
* A file something still points at cannot be deleted from here: doing so
* would leave a broken image on the public site, which is precisely what
* the health check exists to complain about.
*/
public function delete(User $user, $model): bool
{
return parent::delete($user, $model) && ! $model->isReferenced();
}
}